Thanks for reporting -- we should always call attention to random
failures in our various test envs -- such distributed testing casts a
very wide net.
It looks like this is the same failure hit a while back by the nightly build:
https://issues.apache.org/jira/browse/LUCENE-2118
I'm not very concerned about the failure -- it's catching that there
are 11 segments at one level, when the merge policy requires that
there be at most 10; I think it's likely some intermittent corner
case.
But I'll go add some verbosity to the test so we get more details the
next time it fails.
Mike
On Sun, Dec 13, 2009 at 9:11 AM, Erick Erickson <[email protected]> wrote:
> I was running the whole ant-clean-test in a loop last night for
> LUCENE-2122 and had this error in IndexWriter occur once
> in 30+ runs. I now there has been some work on spurious
> failures here lately and thought I'd add this on the chance
> it'd help anyone tracking this issue. Didn't see a JIRA...
>
> I updated the trunk yesterday (12-Dec) afternoon sometime....
>
>
> [junit] Testcase:
> testMaxBufferedDocsChange(org.apache.lucene.index.TestIndexWriterMergePolicy):
> FAILED
> [junit] maxMergeDocs=2147483647; numSegments=11; upperBound=10;
> mergeFactor=10
> [junit] junit.framework.AssertionFailedError: maxMergeDocs=2147483647;
> numSegments=11; upperBound=10; mergeFactor=10
> [junit] at
> org.apache.lucene.index.TestIndexWriterMergePolicy.checkInvariants(TestIndexWriterMergePolicy.java:234)
> [junit] at
> org.apache.lucene.index.TestIndexWriterMergePolicy.testMaxBufferedDocsChange(TestIndexWriterMergePolicy.java:164)
> [junit] at
> org.apache.lucene.util.LuceneTestCase.runBare(LuceneTestCase.java:212)
> [junit]
>
> FWIW
> Erick
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
