lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4146) -Dtests.iters combined with -Dtestmethod never fails?
Date Wed, 20 Jun 2012 19:44:42 GMT


Dawid Weiss commented on LUCENE-4146:

Thanks Hoss, I've been too busy to tackle these issues but I see the light at the end of the
tunnel. Interestingly, this problem has been partially addressed by me before here:

This will print a warning when the filter name contains a seed but the seed hasn't been fixed,
so a new run has totally different set of test names. This happens when you try to narrow
down to a particular test repetition in Eclipse, for example. I print a warning then:

WARNING: Empty set of tests for suite class TestSearch after filters applied. This can be
caused by an attempt to filter tests with a random seed. Use constant seed (-Dtests.seed=deadbeef)
to get a reproducible (and filterable) set of tests.

I filed an issue to do the same in the case above (filtering by fixed method name, but all
method names are expanded with tests.iters:

This should help if anybody encounters this in the future (or from an IDE).
> -Dtests.iters combined with -Dtestmethod never fails?
> -----------------------------------------------------
>                 Key: LUCENE-4146
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>         Attachments:, TEST-org.apache.lucene.TestSearch.iters-no-fail.xml,
> a test that is hardcoded to fail will report succes if you run it with -Dtests.iters

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