With the Python runner (repeatLuceneTest.py in luceneutil), -iters N translates into -Dtests.iters=N, while -jvms M translates into running M JVMs concurrently (for better beasting), so you can combine them to get lots of beasting.
The runner exits once any of the JVMs hit a failure... Mike McCandless http://blog.mikemccandless.com On Tue, Oct 15, 2013 at 9:32 AM, Shai Erera <ser...@gmail.com> wrote: > That's what I've seen too -- it picks the master seed once and then all > iters pick their own derivative seeds. So if the test is random at the > before/after/test level, it usually was enough to find bugs after many > iterations. > > Shai > > > On Tue, Oct 15, 2013 at 4:26 PM, Dawid Weiss <dawid.we...@cs.put.poznan.pl> > wrote: >> >> >> What do you mean? Doesn't it execute the test many times, picking >> >> different >> >> seeds each time? >> >> Only at the test (method) level, at @Before @After hooks and at @Rule >> blocks. @BeforeClass, @AfterClass and class rules are ran with an >> identical seed (because you'd have to effectively reload the class >> under a different class loader or rerun under a different JVM). >> >> This has been long on my list of things to fix, but it's not as >> trivial as it sounds to change it. >> >> Dawid >> >> >> >> > >> > No it does not!!!!!! >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> > For additional commands, e-mail: dev-h...@lucene.apache.org >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
