On Tue, Aug 18, 2009 at 6:57 PM, Dag H. Wanvik<[email protected]> wrote: > [email protected] writes: > >> [Auto-generated mail] >> >> *tinderbox_10.4_16* 805541/2009-08-18 21:13:43 CEST >> >> Failed Tests OK Skip Duration Suite >> ------------------------------------------------------- >> *Jvm: 1.6* >> SunOS-5.10_i86pc-i386 >> 0 2 2 0 85.00% >> org.apache.derbyTesting.functionTests.tests.demo._Suite >> F:1,E:0 10602 10601 0 123.59% >> org.apache.derbyTesting.functionTests.suites.All >> 0 272 272 0 89.78% derbyall >> 0 2 2 0 176.32% >> org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilityCombinations >> Details in >> http://dbtg.foundry.sun.com/derby/test/tinderbox_10.4_16/jvm1.6/testing/Limited/testSummary-805541.html >> Attempted failure analysis in >> >> http://dbtg.foundry.sun.com/derby/test/tinderbox_10.4_16/jvm1.6/FailReports/805541_bySig.html > > The two suggested sigs are already resolved...? A new error? > > Dag > > > >> ------------------------------------------------------- >> >> Changes in >> http://dbtg.foundry.sun.com/derby/test/tinderbox_10.4_16/UpdateInfo/805541.txt >> >> ( All results in http://dbtg.foundry.sun.com/derby/test/ ) >> >
Rick did say that he saw this during his test run before check-in, but he thought it was an unrelated heissenbug. If I remember correctly, this test failure will show up when other tests don't clean up after themselves...Perhaps the new ClassLoaderTest needs adjustment? Myrna
