lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4463) Add support for running the same test method/class many times with different class seeds
Date Sat, 06 Oct 2012 12:55:03 GMT


Michael McCandless commented on LUCENE-4463:

The "scatter tests across a bunch of networked machines" script is here:
... it just uses randomizedrunner to execute the tests, but ssh to distribute each test case
to the N machines.  All JVMs (N per remote machine) pull from a single shared tasks queue,
in order of slowest test to fastest test ... it communicates with randomizedrunner using its
nice stdin/.events "API" :)

It runs [nearly!] all Lucene/Solr tests across N machines and reports any failures ... the
source code is scary and has hardwired constants for my env ... but it makes running all tests
wicked fast.

But that's a very different use case than "beasting a single test" (this issue).  For that
I use
... however, it's single threaded, and does not run on remote machines ... would be fun to
fix that!

bq. He should install Jenkins on his farmhouse machine and then setup a slave

Well I think we need to solve this issue first (how to run many iters of a single testcase
& testmethod, each w/ a different seed)?  Then I agree Jenkins could be used for distribution
instead of ssh + scripts.
> Add support for running the same test method/class many times with different class seeds
> ----------------------------------------------------------------------------------------
>                 Key: LUCENE-4463
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Wish
>          Components: general/build
>            Reporter: Robert Muir
>            Assignee: Dawid Weiss
>         Attachments: LUCENE-4463.patch
> I have a shell script for this, mike has a python script, its annoying :)
> I want to do something like this:
> ant beast -Dtestcase=XXXX -Dtestmethod=YYYY -Diterations=100
> I would be happy with a simple loop that just invokes 'test' somehow: getting a fresh
new JVM to each iteration is desirable anyway (so you get fresh codecs, etc). 
> the -Dtests.iters is not really useful for this because it does not allow -Dtestmethod
and it does not give a fresh jvm.
> bonus points if it can use multiple jvms at the same time though :)

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

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

View raw message