[
https://issues.apache.org/jira/browse/LUCENE-9166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024349#comment-17024349
]
Dawid Weiss commented on LUCENE-9166:
-------------------------------------
Let's leave the stack trace in full. I don't think it harms anyone: the build
is much less chatty anyway and when a failure happens the stack trace is a
fairly important. We can always trim it later.
As for upgrading gradle... Seems like anything I touch recently turns out to
have bugs in it so I'm careful with upgrades if something is working. ;) But
feel free to try it out - altering gradle/wrapper/gradle-wrapper.properties
should do the trick.
> gradle build: test failures need stacktraces
> --------------------------------------------
>
> Key: LUCENE-9166
> URL: https://issues.apache.org/jira/browse/LUCENE-9166
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Priority: Major
> Fix For: master (9.0)
>
> Attachments: LUCENE-9166.patch
>
>
> Test failures are missing the stacktrace. Worse yet, it tells you go to look
> at a separate (very long) filename which also has no stacktrace :(
> I know gradle tries really hard to be quiet and not say anything, but when a
> test fails, that isn't the time or place :)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
