> A new strange test failure: > [junit] Testcase: > testDuringAddDelete(org.apache.lucene.index.TestIndexWriterReader): > FAILED > [junit] null > [junit] junit.framework.AssertionFailedError: null > [junit] at > org.apache.lucene.index.TestIndexWriterReader.testDuringAddDelete(TestInde > xW > riterReader.java:835) > [junit] at > org.apache.lucene.util.LuceneTestCase.runBare(LuceneTestCase.java:208) > [junit] > [junit] > [junit] Test org.apache.lucene.index.TestIndexWriterReader FAILED > > > (occurred in test-tag!) > > It's again a multi-threaded test, after joining all threads, the sum of > hits > is not >0, so added documents were not seen.
The problem is, the same like with the Benchmark test. The test spawns a number of threads. All these threads run half a second and add Documents during that time. The main thread does reopen and searches, and after 0.5 secs it joins all threads. It seems that because of clover analysis and the very slow machine (load!) on Hudson, all threads exited after starting because creating the thread exceeded the limit on getCurrentTimeMillies. Two possibilities: Raise the wait time or better: Replace by a do-while loop in the thread so each thread at least adds a document one time. In main thread also wait 0.5 secs, but after joining all threads again do the search and add to sum. Must be done in trunk and tag. Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
