lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shai Erera <ser...@gmail.com>
Subject Re: Stop iterating if testsFailed
Date Tue, 29 Mar 2011 19:13:33 GMT
Thanks Hoss. This is a good idea. I'll open an issue to track this.

Shai

On Tue, Mar 29, 2011 at 7:11 PM, Chris Hostetter
<hossman_lucene@fucit.org>wrote:

> : 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 :).
>
> suggestion:  add two params...
>
>        tests.iter.min=X
>        tests.iter.max=X
>
> ...make both default to tests.iter as a convinience
> lave the loop iterate up to tests.iter.max and break out if
> (tests.iter.min < counter && testFailed).
>
> people who want to see at least N iters run, but are willing to run up to
> X until/unless there are failures can use tests.iter.min=N,
> tests.iter.max=X
>
> people who want to run until first failure can use tests.iter.min=1,
> tests.iter.max=X.
>
> people who want to see how many failures there are in a set run size can
> (still) use tests.iter=X
>
>
>
> -Hoss
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>

Mime
View raw message