I see. On the other hand, it's a bit annoying when you run with X=100 for the purpose of catching a multi-threaded bug, which occurs after the 2nd iteration ...
I can propose another parameter, tests.iter.break.on.failure, but it's too much I guess :). Shai On Tue, Mar 29, 2011 at 1:38 PM, Robert Muir <rcm...@gmail.com> wrote: > personally I like the existing behavior for a lot of purposes though. > > when i'm trying to write a test for a bug, i use X=100 and look at the > failure percentage. > > On Tue, Mar 29, 2011 at 4:45 AM, Shai Erera <ser...@gmail.com> wrote: > > If I set tests.iter=X, then the test runs X times, even if an instance of > > the test already failed. Would you mind if I change LTC to stop iterating > if > > a test instance failed? The fix is minor -- add 'if (testsFailed) break;' > to > > LTC.runChild(). > > > > Shai > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
