[
https://issues.apache.org/jira/browse/LUCENE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120462#comment-14120462
]
Uwe Schindler commented on LUCENE-5920:
---------------------------------------
Another approach for beasting would be:
We already use a groovy script for beasting. At the beginning of the groovy
script we could set build listeners to silent (log level 0), afterwards
reenable the old value.
The backside is that all output then gets lost. So not helpful if error occurs
(unless junit4 would use severe log levels).
> tweak junit4 output options for 'ant beast'
> -------------------------------------------
>
> Key: LUCENE-5920
> URL: https://issues.apache.org/jira/browse/LUCENE-5920
> Project: Lucene - Core
> Issue Type: Test
> Reporter: Robert Muir
> Fix For: 5.0, 4.11
>
> Attachments: LUCENE-5920-silencer1.patch, LUCENE-5920.patch,
> LUCENE-5920.patch
>
>
> Currently, this outputs way too much, e.g. including all test output for
> every passing run (because this is the behavior when -Dtestcase is set).
> Especially with tests.verbose, this is really annoying as you have output
> from say 200 runs that you don't care about.
> I think ant beast should only show the interesting output for the failing run
> and try to suppress unnecessary output as much as possible for passing ones
> (it should be JUST enough to know your test ran and passed and not ignored,
> e.g. you didnt screw up).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
