avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Simons <leosim...@apache.org>
Subject Re: [GUMP] Build Failure - excalibur-thread
Date Fri, 18 Apr 2003 09:12:50 GMT
I've for now disabled runnig of these tests in gump again. The problem 
with these performance tests is that you want to signal severe 
degradation of performance, which is not possible if you use very huge 
allowed delays. These tests should run on the machine of the average 
developer, which unfortunately seems to be faster than a high-grade sun 
machine (http://nagoya.apache.org/~rubys/gump/excalibur-thread.html).

- Leo

Gump Integration Build wrote:
> test:
>      [echo] Performing Unit Tests
>     [junit] Testcase: test10Workers100Tasks took 2.115 sec
>     [junit] 	FAILED
>     [junit] Time to complete all tasks, 2105, was not within 100ms of the expected time,
>     [junit] junit.framework.AssertionFailedError: Time to complete all tasks, 2105, was
not within 100ms of the expected time, 2000
>     [junit] 	at org.apache.avalon.excalibur.thread.impl.test.ResourceLimitingThreadPoolTestCase.commonTest(ResourceLimitingThreadPoolTestCase.java:210)
>     [junit] 	at org.apache.avalon.excalibur.thread.impl.test.ResourceLimitingThreadPoolTestCase.test10Workers100Tasks(ResourceLimitingThreadPoolTestCase.java:104)
>     [junit] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     [junit] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     [junit] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message