Hi Adrien,
Look at "ant test-help":
[help] # Use repeatable suite order on slave JVMs (disables job stealing).
[help] ant -Dtests.dynamicAssignmentRatio=0 test
This will keep the test-JVM assignment constant for a given seed.
Jenkins by default doesn't use this (to allow better load-balancing
based on historical data) so you won't be able to reproduce its test
order identically, but if you experiment with a few fixed seeds and
the above setting you may hit the same problem again (and then
reproduce the assignment).
Dawid
On Mon, Mar 2, 2015 at 10:45 AM, Adrien Grand <[email protected]> wrote:
> Hi,
>
> I'm trying to reproduce the TestScorerPerf timeout. In order to do
> this I would like to have tests running in the same order as on
> Jenkins. On
> http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/11738/consoleFull
> tests run in 2 JVMs and the first test to run on J0 is
> org.apache.lucene.index.TestCodecUtil.
>
> I tried to run tests on the same svn revision (1663038) with the same
> seed/jvms but get a different test order:
>
> $ ant test -Dtests.jvms=2 -Dtests.seed=E106E3FEC03B137
> -Dtests.multiplier=3 -Dtests.slow=true
>
> But the first test that runs on J0 is
> org.apache.lucene.index.TestIndexWriterOutOfMemory. Is there a
> parameter that I am missing?
>
> --
> Adrien
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
