mikemccand commented on PR #14167:
URL: https://github.com/apache/lucene/pull/14167#issuecomment-2610089955
> Frustratingly, the seeded failures do not seem to be repeatable.
Hmm that is bad ... it means there is a test bug or test infra bug (separate
from the scary bug this test is chasing!)?
Oh, maybe force `SerialMergeScheduler` to your `RandomIndexWriter`? Since
`CMS` (Lucene's default and RIW will sometimes pick that) launches threads and
we don't know how to determinize JVM's/OS's thread scheduling, that might
explain the non-reproducibility? E.g.:
```
IndexWriterConfig iwc = LuceneTestCase.newIndexWriterConfig(r, new
MockAnalyzer(r)), true, r.nextBoolean();
iwc.setMergeScheduler(new SerialMergeScheduler());
RandomIndexWriter riw = new RandomIndexWriter(random(), dir, iwc);
```
or so?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
