lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3785) Replace ant macros for running concurrent tests with ant-junit4.
Date Sun, 19 Feb 2012 21:42:34 GMT


Dawid Weiss commented on LUCENE-3785:

I've found and fixed the gson issue. I re-run ant test (no nightly though) 10 times, everything
went fine -- 7 successful builds and 3 errors (BasicZkTest.testBasic, BasicDistributedZkTest.testDistribSearch),
but these are not caused by the testing framework I guess.

I'm ready to merge this work with the trunk once I receive acks (this will probably break
your existing forks/ branches/patches if you have any -- there's quite a lot of tiny changes).

I will attach a patch to this issue for completeness, but it'll be a huge blob (just warning).
> Replace ant macros for running concurrent tests with ant-junit4.
> ----------------------------------------------------------------
>                 Key: LUCENE-3785
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Sub-task
>          Components: general/build, general/test
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>            Priority: Minor
>             Fix For: 4.0
>         Attachments: failure-cases.patch, junit4-1.txt, junit4-2.txt, line-per-test.txt,
lucene-tests.txt, trunk1.txt, trunk2.txt
> ant-junit4 is an ANT task for running tests in parallel (on slave JVMs). Its advantages
over the current macros:
> - dynamic load balancing based on historical test runs and current execution (job-stealing),
> - jvm-crash resilience (I wrote tests that actually crash a slave jvms to make sure such
an event is reported appropriately),
> - nicer console reporting (no need for syserrs on LuceneTestCase level).
> More documentation and info will follow as I roll out a patch.
> NOTE. The code for this issue is being developed at:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message