Opened LUCENE-4646. Shai
On Sat, Dec 22, 2012 at 3:25 AM, Michael McCandless < [email protected]> wrote: > Hrmph. > > It looks like the test really did fail :( > > It expected only 2 insanities but there were 4 ... not sure what's up > and I'm on heavy vacation mode now ... can you open an issue? I'll > try to have a look when I'm back ... > > Mike McCandless > > http://blog.mikemccandless.com > > On Fri, Dec 21, 2012 at 3:04 PM, Shai Erera <[email protected]> wrote: > >> did the test really cause a BUILD FAILED > > > > > > Yes: > > > > [junit4:junit4] Tests with failures: > > [junit4:junit4] - > > org.apache.lucene.util.TestFieldCacheSanityChecker.testInsanity1 > > [junit4:junit4] > > [junit4:junit4] > > [junit4:junit4] JVM J0: 3.77 .. 374.56 = 370.79s > > [junit4:junit4] JVM J1: 3.81 .. 376.50 = 372.70s > > [junit4:junit4] JVM J2: 3.81 .. 382.46 = 378.64s > > [junit4:junit4] JVM J3: 3.77 .. 374.77 = 371.00s > > [junit4:junit4] Execution time total: 6 minutes 22 seconds > > [junit4:junit4] Tests summary: 323 suites, 1863 tests, 1 failure, 23 > ignored > > (11 assumptions) > > > > BUILD FAILED > > D:\dev\lucene\lucene-trunk\lucene\build.xml:50: The following error > occurred > > while executing this line: > > D:\dev\lucene\lucene-trunk\lucene\common-build.xml:1175: The following > error > > occurred while executing this line: > > D:\dev\lucene\lucene-trunk\lucene\common-build.xml:840: There were test > > failures: 323 suites, 1863 tests, 1 failure, 23 ignored (11 assumptions) > > > > The test fails on this line: > > > > assertEquals("wrong number of entries in cache error", 2, > > insanity[0].getCacheEntries().length); > > > > It looks like a test failure to me, though I don't really know what the > test > > does. Thanks for the explanation that it "tests the tests" :) > > > > Shai > > > > > > On Fri, Dec 21, 2012 at 2:28 PM, Michael McCandless > > <[email protected]> wrote: > >> > >> 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] > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
