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

Uwe Schindler edited comment on LUCENE-5920 at 9/4/14 8:16 AM:
---------------------------------------------------------------

This is my idea (disable logging on the ant level).

This is how it looks now when everything goes well:

{noformat}
$ ant beast -Dbeast.iters=10 -Dtestcase=TestVersion
[...]
-init-totals:

-beast:
  [beaster] Beast round: 1
  [beaster] Beast round: 2
  [beaster] Beast round: 3
  [beaster] Beast round: 4
  [beaster] Beast round: 5
  [beaster] Beast round: 6
  [beaster] Beast round: 7
  [beaster] Beast round: 8
  [beaster] Beast round: 9
  [beaster] Beast round: 10
  [beaster] Beasting finished.

-check-totals:

beast:

BUILD SUCCESSFUL
Total time: 23 seconds
{noformat}

Unfortunately this is how it looks when it goes wrong:

{noformat}
$ ant beast -Dbeast.iters=10 -Dtestcase=TestVersion -Dtests.codec=foobar
[...]
-init-totals:

-beast:
  [beaster] Beast round: 1

BUILD FAILED
C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\lucene\common-build.xml:1352: The 
following error occurred while executing this line:
C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\lucene\common-build.xml:1347: The 
following error occurred while executing this line:
C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\lucene\common-build.xml:959: There were 
test failures: 1 suite, 0 tests, 1 suite-level error

Total time: 5 seconds
{noformat}

As you see, you get no idea what was wrong, nor get you a tests.seed on 
failure. This looks like caused by junit4 not logging the error messages with a 
log level of at minimum WARN, which you explained. Maybe all System.err stuff 
should be printed with error log level.


was (Author: thetaphi):
This is my idea (disable logging on the ant level).

This is how it looks now when everything goes well:

{noformat}
$ ant beast -Dbeast.iters=10 -Dtestcase=TestVersion
[...]
-init-totals:

-beast:
  [beaster] Beast round: 1
  [beaster] Beast round: 2
  [beaster] Beast round: 3
  [beaster] Beast round: 4
  [beaster] Beast round: 5
  [beaster] Beast round: 6
  [beaster] Beast round: 7
  [beaster] Beast round: 8
  [beaster] Beast round: 9
  [beaster] Beast round: 10
  [beaster] Beasting finished.

-check-totals:

beast:

BUILD SUCCESSFUL
Total time: 23 seconds
{noformat}

Unfortunately this is how it looks when it goes wrong:

{noformat}
$ ant beast -Dbeast.iters=10 -Dtestcase=TestVersion -Dtests.codec=foobar
[...]
-init-totals:

-beast:
  [beaster] Beast round: 1

BUILD FAILED
C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\lucene\common-build.xml:1352: The 
following error occurred while executing this line:
C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\lucene\common-build.xml:1347: The 
following error occurred while executing this line:
C:\Users\Uwe 
Schindler\Projects\lucene\trunk-lusolr1\lucene\common-build.xml:959: There were 
test failures: 1 suite, 0 tests, 1 suite-level error

Total time: 5 seconds
{noformat}

As you see, you get no idea what was wrong. This looks like caused by junit4 
not logging the error messages with a log level of at minimum WARN.

> 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-silencer2.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to