[ https://issues.apache.org/jira/browse/LUCENE-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012995#comment-13012995 ]
Shai Erera commented on LUCENE-3002: ------------------------------------ Since it's a trivial change, I plan to commit this either later today or tomorrow. > Add tests.iter.min to improve controlling tests.iter's behavior > --------------------------------------------------------------- > > Key: LUCENE-3002 > URL: https://issues.apache.org/jira/browse/LUCENE-3002 > Project: Lucene - Java > Issue Type: Test > Components: Tests > Reporter: Shai Erera > Assignee: Shai Erera > Priority: Minor > Fix For: 3.2, 4.0 > > Attachments: LUCENE-3002.patch > > > As discussed here: > http://lucene.472066.n3.nabble.com/Stop-iterating-if-testsFailed-td2747426.html, > this issue proposes to add tests.iter.min in order to allow one better > control over how many iterations are run: > * Keep tests.iter as it is today > * Add tests.iter.min (default to tests.iter) to denote that at least N > instances of the test should run until there's either a failure or tests.iter > is reached. > If one wants to run until the first failure, he can set tests.iter.min=1 and > tests.iter=X -- up to X instances of the test will run, until the first > failure. > Similarly, one can set tests.iter=N to denote that at least N instances > should run, regardless if there were failures, but if after N runs a failure > occurred, the test should stop. > Note: unlike what's proposed on the thread, tests.iter.max is dropped from > this proposal as it's exactly like tests.iter, so no point in having two > similar parameters. > I will work on a patch tomorrow. -- This message is automatically generated by JIRA. 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