[
https://issues.apache.org/jira/browse/LUCENE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121053#comment-14121053
]
Uwe Schindler commented on LUCENE-5920:
---------------------------------------
I think this was a misunderstanding. You are talking about listeners to events
and log events in JUnit4.
The "fast approach" here was to disable logging completely in ANT: Raise the
log level to ERROR. My problem was then caused by the fact that Ant then did
not show anything anymore. The approach here was to let Ant itsself supress
logging. The groovy beaster script can do this easily.
I was referring to this approach:
http://stackoverflow.com/questions/5462732/make-ant-quiet-without-the-q-flag
(although the scripts inside are "wrong", because they miss correct checks and
assume that there is only one build listener).
Ant's loggers can only print whole lines, how to work around that?
> 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]
