[
https://issues.apache.org/jira/browse/LUCENE-9166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024344#comment-17024344
]
Robert Muir commented on LUCENE-9166:
-------------------------------------
[~dweiss] I think this is actually working around
https://github.com/gradle/gradle/issues/11220 which looks like it was fixed in
6.1.1
Still I am skeptical of the filtering :) But alternatively we could revert this
commit and upgrade and it would solve at least the particular problem that I
had here. Looks like the fix simply checks for where the filter would remove
the whole stacktrace completely...
> 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: [email protected]
For additional commands, e-mail: [email protected]