dweiss opened a new issue, #14066: URL: https://github.com/apache/lucene/issues/14066
### Description #14049 added randomization of codec params but as part of that it may spin up new threads when ForkJoinPool.commonPool is started. We have no control over these threads but they do cause test failures as in here:  I think we can safely assume common pool's threads surviving the test's scope are not interesting for us to detect and any leftover threads/ runnables will just eventually complete and die (?). I feel tempted to ignore those threads by adding them to QuickPatchThreadsFilter. If we want to ensure nothing survives the test's scope, we could add a rule to LuceneTestCase that would wait (after the suite completes) until the active count of workers in the common pool is zero. ### Version and environment details _No response_ -- 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.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
