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-3753) Restructure the Lucene build system
Date Mon, 06 Feb 2012 20:54:59 GMT


Dawid Weiss commented on LUCENE-3753:

Yes, this is what Mike's python magic does -- puts a fraction of all tests on each slave,
then assigns on-demand. I reimplemented this in Java and it works quite nice as it can even
consume precomputed statistics to make better estimates. The problem is as always in details
(which I won't trouble you with at the moment). Robert is also right that re-running with
different parameters/ JVM settings/ classpath will require multiple runs... for a moment I
had a hope to neglect this :)

The speedups aren't dramatic, especially after Robert worked on the longest tests, so this
is not a huge priority. Interestingly, Maven's latest release of surefire also includes an
option to do balanced parallel tests (on separate vms). Didn't experiment with it yet.
> Restructure the Lucene build system
> -----------------------------------
>                 Key: LUCENE-3753
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: general/build
>    Affects Versions: 3.6, 4.0
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>         Attachments: LUCENE-3753.patch, LUCENE-3753.patch, LUCENE-3753.patch
> Split out separate core/, test-framework/, and tools/ modules, each with its own build.xml,
under the lucene/ directory, similar to the Solr restructuring done in SOLR-2452.

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