lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4160) Bring back the functional equivalent of tests.iters.min
Date Thu, 28 Jun 2012 09:31:43 GMT


Dawid Weiss commented on LUCENE-4160:

Thanks for the clarification, Hoss. We could also do:

-Dtests.iters=X -Dtests.minfailures=Y

What this would do is repeat everything X times but ignore anything after the first Y failures...
So if you'd like to quickly abort after the first failure, you'd do:

-Dtests.iters=X -Dtests.minfailures=1

and if you wanted more (for whatever reason) you could wait for more, but still abort earlier
than X. I'll just provide a patch for this and we'll see how it turns out in practice.
> Bring back the functional equivalent of tests.iters.min
> -------------------------------------------------------
>                 Key: LUCENE-4160
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: general/test
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>            Priority: Trivial
>             Fix For: 5.0
> What is needed is effectively saying: "repeat this test N times, but stop once you hit
a failure".
> Previously it was "tests.iters.min=X" which is (still) kind of confusing to me because
I don't understand how "X" is related to the original question.
> I propose to implement a boolean "tests.fastfail" which would ignore any tests running
on the same JVM after the first failure has been hit.
> Those with fond memories of "tests.iters.min" speak up, please.

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