lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-5920) tweak junit4 output options for 'ant beast'
Date Wed, 03 Sep 2014 20:17:52 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Muir updated LUCENE-5920:
--------------------------------
    Attachment: LUCENE-5920.patch

updated patch. i fixed all the conditionals with else in common-build.xml

I think we should do this as a start, for the tough bugs requiring verbose?

Later, maybe we can do something fancier like a custom listener even. But for now this makes
it really usable for such 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
>         Attachments: 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message