Closed mikemccand closed 5 years ago
I'm not sure this old feature has a meaning with current Lucene's segments management strategy, but I attached a patch that uses NoMergePolicy to prevent segment merges when testing isOptimized()
method.
[Legacy Jira: Tomoko Uchida (@mocobeta) on Oct 05 2019]
Commit 42ff080c84389efcbb1dd62d8d59b02dedbb43ae in lucene-solr's branch refs/heads/master from Tomoko Uchida https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=42ff080
LUCENE-8998: Fix OverviewImplTest.testIsOptimized reproducible failure
[Legacy Jira: ASF subversion and git services on Oct 05 2019]
Commit 0299e4c65d3d7d6c00ae5cfd7b974d5eaa84d035 in lucene-solr's branch refs/heads/branch_8x from Tomoko Uchida https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=0299e4c
LUCENE-8998: Fix OverviewImplTest.testIsOptimized reproducible failure
[Legacy Jira: ASF subversion and git services on Oct 05 2019]
Thank you @hossman
for reporting.
[Legacy Jira: Tomoko Uchida (@mocobeta) on Oct 05 2019]
Closing after the 9.0.0 release
[Legacy Jira: Adrien Grand (@jpountz) on Dec 08 2021]
The following seed reproduces reliably for me on master...
(NOTE: the
ERROR StatusLogger
messages include the one about the AccessControlException occur even with other seeds when the test passes)This method fails on that seed regardless of wether
tests.method
is used, or if all methods in that class are runLegacy Jira details
LUCENE-8998 by Chris M. Hostetter on Oct 02 2019, resolved Oct 05 2019 Attachments: LUCENE-8998.patch