[ 
https://issues.apache.org/jira/browse/LUCENE-9166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024435#comment-17024435
 ] 

Robert Muir commented on LUCENE-9166:
-------------------------------------

Interesting. I feel like this worked for the elasticsearch gradle build a long 
time ago. I can't remember how it worked, but I feel like it was still using 
your junit runner to actually run the tests versus the built-in gradle test 
support? Maybe it would solve several of our problems?

> 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

Reply via email to