msokolov opened a new issue, #13829: URL: https://github.com/apache/lucene/issues/13829
### Description I've noticed that some tests fail when `tests.iters` is set to a highish value (like 20) because stdout grows above the allowed threshold. I assume this is something we'd want to fix, but I'm not clear how to go about it exactly. Some tests I've seen fail are: `TestDemo.testIndexSearch` (IndexFiles outputs the names of files as they are added to the index); `TestIndexWriter.testDocValuesMixedSkippingIndex` (prints a stack trace, I think it's expected?); `TestTransactions` prints out an iteration count. We could work on reducing the amount of printing, but I wonder if the test framework should ideally multiply the acceptable stdout threshold by the iters? ### Version and environment details all versions, probably -- 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
