[
https://issues.apache.org/jira/browse/LUCENE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121164#comment-14121164
]
Dawid Weiss commented on LUCENE-5920:
-------------------------------------
> As you see, you get no idea what was wrong, nor get you a tests.seed on
> failure.
You always get the full test stream from this test listener:
{code}
<!-- Emits status on errors and failures only. -->
<junit4:report-text
file="@{junit.output.dir}/tests-failures.txt"
{code}
> This looks like caused by junit4 not logging the error messages with a log
> level of at minimum WARN, which you explained.
Well, I don't consider this a warning. Also, it'll be difficult to separate and
display just the reproduce-info because it's part of a regular stream from a
subprocess. You can always tail tests-failures.txt or tests-report.txt -- it
contains full streams from all tests.
> 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-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: [email protected]
For additional commands, e-mail: [email protected]
