[
https://issues.apache.org/jira/browse/LUCENE-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059439#comment-13059439
]
Shai Erera commented on LUCENE-3268:
------------------------------------
Ok I found the problem. The test relies on Lucene doc IDs to assert the
results. So at first I went for disabling merges (because they removed deleted
docs and screwed up the IDs), but that didn't help entirely because for some
seeds, a whole segment turned up to be deleted, and thus dropped, screwing up
the IDs as well.
So I fixed the test to add a stored field to all the docs that are deleted, and
then instead of asserting that the returned docID was not marked for deletion,
I assert that the returned document does not contain that field.
I ran the test w/ -Dtests.iter=10000 (10K) and it didn't find any bad seed.
Previously it hunted them pretty quickly !
I'll commit a fix shortly to 3x and trunk.
> TestScoredDocIDsUtils.testWithDeletions test failure
> ----------------------------------------------------
>
> Key: LUCENE-3268
> URL: https://issues.apache.org/jira/browse/LUCENE-3268
> Project: Lucene - Java
> Issue Type: Bug
> Components: modules/facet
> Reporter: Robert Muir
> Assignee: Shai Erera
> Fix For: 3.4, 4.0
>
>
> ant test -Dtestcase=TestScoredDocIDsUtils -Dtestmethod=testWithDeletions
> -Dtests.seed=-2216133137948616963:2693740419732273624 -Dtests.multiplier=5
> In general, on both 3.x and trunk, if you run this test with -Dtests.iter=100
> it tends to fail 2% of the time.
--
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
