From adaf6106717d71fec2444d7d7f1bae2886b19b71 Mon Sep 17 00:00:00 2001 From: Robert Muir Date: Sat, 4 Dec 2021 14:21:45 -0500 Subject: [PATCH] tone down TestIndexWriter.testMaxCompletedSequenceNumber in non-nightly (#506) this test currently indexes up to 600 docs for each thread. --- .../core/src/test/org/apache/lucene/index/TestIndexWriter.java | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lucene/core/src/test/org/apache/lucene/index/TestIndexWriter.java b/lucene/core/src/test/org/apache/lucene/index/TestIndexWriter.java index d80b1022c0f..49b537999c1 100644 --- a/lucene/core/src/test/org/apache/lucene/index/TestIndexWriter.java +++ b/lucene/core/src/test/org/apache/lucene/index/TestIndexWriter.java @@ -4279,7 +4279,8 @@ public class TestIndexWriter extends LuceneTestCase { IndexWriter writer = new IndexWriter(dir, newIndexWriterConfig()); SearcherManager manager = new SearcherManager(writer, new SearcherFactory())) { CountDownLatch start = new CountDownLatch(1); - int numDocs = 100 + random().nextInt(500); + int numDocs = + TEST_NIGHTLY ? TestUtil.nextInt(random(), 100, 600) : TestUtil.nextInt(random(), 10, 60); AtomicLong maxCompletedSeqID = new AtomicLong(-1); Thread[] threads = new Thread[2 + random().nextInt(2)]; for (int i = 0; i < threads.length; i++) {