Leo Simons wrote:
nope! I've tried it on a couple of machines, and a normal 'ant test'
doesn't result in failure, whereas running GUMP (either completely or
using '/data/gump/bin/build excalibur-compatibility', which just
rebuilds the excalibur-compatibility project and nothing else) does
resul
Leo Simons wrote:
> http://lsd.student.utwente.nl/gump/excalibur-compatibility.html:
>
> [junit] Testcase: testDeadLock took 0.328 sec
> [junit] FAILED
> [junit] null
> [junit] junit.framework.AssertionFailedError
> [junit] at
org.apache.avalon.excalibur.concurrent.test.ReadWriteLockTestCase.test
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Leo Simons
>
> Leo Sutic wrote:
> > If you run "ant test" on the compatibility project (and not GUMP,
> > which you seem to be running), do you still get a failure there?
>
> nope! I've tried it on a couple of machines, and a normal 'ant test
Leo Sutic wrote:
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Leo Simons
is this a known issue?
No, it's not. I am unable to duplicate that error.
You seem to have problems with many testcases that involve multiple
threads.
the failure with the monitor thing was on a different machine, diffe
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Leo Simons
>
> is this a known issue?
No, it's not. I am unable to duplicate that error.
You seem to have problems with many testcases that involve multiple
threads.
If you run "ant test" on the compatibility project (and not GUMP, which
you s
http://lsd.student.utwente.nl/gump/excalibur-compatibility.html:
[junit] Testcase: testDeadLock took 0.328 sec
[junit] FAILED
[junit] null
[junit] junit.framework.AssertionFailedError
[junit] at
org.apache.avalon.excalibur.concurrent.test.ReadWriteLockTestCase.testDeadLock(ReadWriteLockTestCase.j
