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 13:13:51 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

Here's a patch. This attacks the worst of it, so you don't see full test output for passing
runs.

It would be great if we could further reduce the noise, as each passing run still does a lot
of useless stuff like topHints, but I don't know how to cleanly do it.

{noformat}
   [junit4] <JUnit4> says ciao! Master seed: C8AD36CBB2C5BBC0
   [junit4] Executing 1 suite with 1 JVM.
   [junit4] 
   [junit4] Started J0 PID(10546@beast).
   [junit4] OK      0.30s | TestDemo.testDemo
   [junit4] JVM J0:     0.37 ..     1.51 =     1.14s
   [junit4] Execution time total: 1.53 sec.
   [junit4] Tests summary: 1 suite, 1 test
     [echo] 5 slowest tests:
[junit4:tophints]  30.50s | org.apache.lucene.codecs.lucene410.TestLucene410DocValuesFormat
[junit4:tophints]  27.76s | org.apache.lucene.codecs.compressing.TestCompressingTermVectorsFormat
[junit4:tophints]  19.49s | org.apache.lucene.index.TestMixedDocValuesUpdates
[junit4:tophints]  14.29s | org.apache.lucene.codecs.perfield.TestPerFieldDocValuesFormat
[junit4:tophints]  13.93s | org.apache.lucene.index.TestIndexWriterExceptions
{noformat}

> 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
>
>
> 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