[ https://issues.apache.org/jira/browse/LUCENE-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403012#comment-13403012 ]
Robert Muir commented on LUCENE-4160: ------------------------------------- I think i originally caused the complexity by wanting to still have a way to run a test like 1000 times and look at the failure rate. This is occasionally useful: e.g. this test fails 2% of the time and I improved the test to fail 10% of the time or whatever :) But really I think its more useful in general to have 'fastfail' on by default... especially now that in general tests are reproducing a lot better than before... > Bring back the functional equivalent of tests.iters.min > ------------------------------------------------------- > > Key: LUCENE-4160 > URL: https://issues.apache.org/jira/browse/LUCENE-4160 > Project: Lucene - Java > Issue Type: Bug > Components: general/test > Reporter: Dawid Weiss > Assignee: Dawid Weiss > Priority: Trivial > Fix For: 5.0 > > Attachments: LUCENE-4160.patch > > > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org