The two errors are obviously my fault, caused by the check-in for
DERBY-3936.
I'll have a look tomorrow, but at first sight it looks like it's failing
because I haven't used the new class anywhere in the engine code and
therefore the class isn't included in the jar.
I think I ran my tests tests with another patch in the sandbox. The
problem is temporary in the sense that it will go away when the new code
is used, but I might have to provide a work-around until the next proper
patch is ready.
Sorry for the noise.
--
Kristian
[EMAIL PROTECTED] wrote:
[Auto-generated mail]
*tinderbox_trunk16* 718936/2008-11-19 12:52:26 CET
Failed Tests OK Skip Duration Suite
-------------------------------------------------------
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0 2 2 0 115.78%
org.apache.derbyTesting.functionTests.tests.demo._Suite
F:0,E:2 10850 10848 0 2298.85%
org.apache.derbyTesting.functionTests.suites.All
0 235 235 0 111.25% derbyall
0 2 2 0 215.40%
org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilityCombinations
Details in http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/testSummary-718936.html
Attempted failure analysis in
http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/FailReports/718936_bySig.html
-------------------------------------------------------
Changes in http://dbtg.thresher.com/derby/test/tinderbox_trunk16/UpdateInfo/718936.txt
( All results in http://dbtg.thresher.com/derby/test/ )
