|
From: Peter C. <cen...@ri...> - 2002-09-12 19:05:46
|
Just for the hell of it, I ran "ant update clean compile test"
on my Mac OS 10.1.5 iBook. The first test case took 76s, which
is quite excessive, but I figure that probably includes slow Mac
OS X JVM loading time. The other quirk is a little harder to
explain away. Can anyone duplicate this failure? I'll send my
.drjava to the curious.
[junit] Testcase: testLimitOneByOne took 0.075 sec
[junit] FAILED
[junit] Number of available compilers expected:<0> but was:<1>
[junit] junit.framework.AssertionFailedError: Number of
available compilers expected:<0> but was:<1>
[junit] at junit.framework.Assert.fail(Assert.java:51)
[junit] at junit.framework.Assert.failNotEquals(Assert.java:234)
[junit] at junit.framework.Assert.assertEquals(Assert.java:68)
[junit] at junit.framework.Assert.assertEquals(Assert.java:181)
[junit] at
edu.rice.cs.drjava.model.compiler.CompilerRegistryTest._getCompilersAfterDisablingSome(
CompilerRegistryTest.java:209)
[junit] at
edu.rice.cs.drjava.model.compiler.CompilerRegistryTest._getCompilersAfterDisablingOne(
CompilerRegistryTest.java:189)
[junit] at
edu.rice.cs.drjava.model.compiler.CompilerRegistryTest.testLimitOneByOne
(CompilerRegistryTest.java:127)
+ junit stack overhead . . .
--
Peter
|