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-compatibility
Date Thu, 03 Apr 2003 18:31:28 GMT
grmbl. It is obvious to me by now that the concurrency code can lead to 
deadlocks, but after lots of testing I still haven't isolated when it 
occurs. We can either spend more time debugging the code (which I'm not 
really feeling like; this stuff makes my head hurt) or disable the 
deadlock test.

If no-one feels like fixing the code, is it okay if I disable the test?


Gump Integration Build wrote:
>     [junit] Testcase: testDeadLock took 0.119 sec
>     [junit] 	FAILED
>     [junit] null
>     [junit] junit.framework.AssertionFailedError
>     [junit] 	at org.apache.avalon.excalibur.concurrent.test.ReadWriteLockTestCase.testDeadLock(ReadWriteLockTestCase.java:410)
>     [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)
>     [junit] Testcase: testDeadLock

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

View raw message