I agree, it happens always with tests.nightly=true and multiplicator>1. I 
retriggered a nightly Jenkins build, same error message. The failure mail 
should arrive shortly J

 

-----

Uwe Schindler

H.-H.-Meier-Allee 63, D-28213 Bremen

 <http://www.thetaphi.de/> http://www.thetaphi.de

eMail: [email protected]

 

From: [email protected] [mailto:[email protected]] On Behalf Of 
Martijn v Groningen
Sent: Sunday, January 01, 2012 12:50 PM
To: [email protected]
Subject: Re: [JENKINS] Lucene-trunk - Build # 1786 - Failure

 

I think this is just a broken test case. If this test is ran with: 
"-Dtests.seed=-289aae8d40093437:-2c1c9ffc76ccb3bd:71f64018e9abbebb 
-Dtests.multiplier=3 -Dtests.nightly=true" then 1300 documents with term "aaa" 
are indexed. During searching the maximum number of documents to retrieve is 
hard coded to 1000. 

In that case the assertion on line 460 fails. 

 

Replacing:

ScoreDoc[] hits = searcher.search(new TermQuery(new Term("field", "aaa")), 
null, 1000).scoreDocs;

with:

ScoreDoc[] hits = searcher.search(new TermQuery(new Term("field", "aaa")), 
null, n*100).scoreDocs;

will fix this failure.

 

Martijn

On 1 January 2012 05:10, Apache Jenkins Server <[email protected]> 
wrote:

Build: https://builds.apache.org/job/Lucene-trunk/1786/

1 tests failed.
REGRESSION:  org.apache.lucene.index.TestIndexWriter.testDiverseDocs

Error Message:
expected:<1300> but was:<1000>

Stack Trace:
junit.framework.AssertionFailedError: expected:<1300> but was:<1000>
       at 
org.apache.lucene.util.LuceneTestCaseRunner.runChild(LuceneTestCaseRunner.java:165)
       at 
org.apache.lucene.util.LuceneTestCaseRunner.runChild(LuceneTestCaseRunner.java:57)
       at 
org.apache.lucene.index.TestIndexWriter.testDiverseDocs(TestIndexWriter.java:459)
       at 
org.apache.lucene.util.LuceneTestCase$3$1.evaluate(LuceneTestCase.java:528)




Build Log (for compile errors):
[...truncated 12691 lines...]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to