[
https://issues.apache.org/jira/browse/LUCENE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120774#comment-14120774
]
Robert Muir commented on LUCENE-5920:
-------------------------------------
Hi Uwe, thanks for the improvement!
About your additional idea, i think we can do it, but I think we need to fix
this check to happen on the first iteration?
{noformat}
/home/rmuir/workspace/trunk-checkmerge/lucene/common-build.xml:1373: Not even a
single test was executed (a typo in the filter pattern maybe)?
{noformat}
Currently, this does not happen until the end of the beasting (I don't know
why). its important in case you screw up: typo tests.method, tests.class, or
the thing is Nightly or Ignored.
If we fix this, we don't need any of the current output, just maybe a "." or
some other kind of status bar to see progress.
> 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]
