Do anyone else see this?
I see this in all(?) test runs since the tinderbox test run on svn 507489.
(
http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/Limited/testSummary-507489.html
)
That specific test run I aborted after ~6 hours.
(Test started ~11:29:52.655 GMT, killed ~17:27:23.428 GMT)
The duration of suites.All on this platform has been 42-46 minutes in
the previous 4 successful runs.
CPU utilization now is close to 100%:
.. .. 97.0 ... java junit.textui.TestRunner
org.apache.derbyTesting.functionTests.suites.All
In another test run
http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-507650.html
/ Linux-2.6.9-34.ELsmp_x86, suites.All finished in ~4 times the
previously seen duration time.
--
Ole Solberg, Database Technology Group,
Sun Microsystems, Trondheim, Norway
