Hmm, this is actually "expected": this is a "who tests the tests" test :)

Ie, it intentionally sets up FC insanity and then confirms test
framework catches this failure and fails the test.

But, it should not cause a REAL failure ... did the test really cause
a BUILD FAILED?  Or was it just noisy output?  Eg, if you were you
running with -Dtests.showsuccess=true (or, running just a single
testcase, which I think also turns on all output) then you'd see the
output ...

Mike McCandless

http://blog.mikemccandless.com

On Fri, Dec 21, 2012 at 4:47 AM, Shai Erera <[email protected]> wrote:
> Hi
>
> I've hit this while running tests:
>
> [junit4:junit4] Suite: org.apache.lucene.util.TestFieldCacheSanityChecker
> [junit4:junit4]   2> NOTE: reproduce with: ant test
> -Dtestcase=TestFieldCacheSanityChecker -Dtests.method=testInsanity1
> -Dtests.seed=7E0EF33CC742369A -Dtests.slow=true -Dtests.locale=sr_RS_Latn
> -Dtests.timezone=ECT -Dtests.file.encoding=UTF-8
> [junit4:junit4] FAILURE 1.30s J0 | TestFieldCacheSanityChecker.testInsanity1
> <<<
> [junit4:junit4]    > Throwable #1: java.lang.AssertionError: wrong number of
> entries in cache error expected:<2> but was:<4>
> [junit4:junit4]    >    at
> __randomizedtesting.SeedInfo.seed([7E0EF33CC742369A:15B02AB0AB1CB68A]:0)
> [junit4:junit4]    >    at org.junit.Assert.fail(Assert.java:93)
> [junit4:junit4]    >    at org.junit.Assert.failNotEquals(Assert.java:647)
> [junit4:junit4]    >    at org.junit.Assert.assertEquals(Assert.java:128)
> [junit4:junit4]    >    at org.junit.Assert.assertEquals(Assert.java:472)
> [junit4:junit4]    >    at
> org.apache.lucene.util.TestFieldCacheSanityChecker.testInsanity1(TestFieldCacheSanityChecker.java:135)
>
> Failed to reproduce with the seed w/ and w/o tests.method. Tried w/
> tetss.iters=100, but did not reproduce.
>
> I can look at it later, but in case someone who knows this code better want
> to look too ...
>
> Shai

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

Reply via email to