thread.DefaultRunnableManagerTestCase failing

[Jorg Heymans <jh...@domek.be>]

Hi,

It seems that this testcase fails __sometimes__, is this known behaviour ?


Running org.apache.cocoon.components.thread.DefaultRunnableManagerTestCase
Exception in thread "Thread-10" junit.framework.AssertionFailedError:
  Unexpected method call debug("Executing command EasyMock for interface
java.lang.Runnable in pool "mypool", schedule with interval=100"):
    debug("Executing command EasyMock for interface java.lang.Runnable in
pool "mypool", schedule with interval=100"): expected: 0, actual: 1
    debug("Exiting loop"): expected: 1, actual: 0
        at 
org.easymock.internal.ObjectMethodsFilter.invoke(ObjectMethodsFilter.java:44
)
        at $Proxy6.debug(Unknown Source)
        at 
org.apache.cocoon.components.thread.DefaultRunnableManager$ExecutionInfo.exe
cute(DefaultRunnableManager.java:749)
        at 
org.apache.cocoon.components.thread.DefaultRunnableManager.run(DefaultRunnab
leManager.java:441)
        at 
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:613)
junit.framework.AssertionFailedError:
  Unexpected method call isDebugEnabled():
    isDebugEnabled(): expected: 0, actual: 1
    debug("Exiting loop"): expected: 1, actual: 0
        at 
org.easymock.internal.ObjectMethodsFilter.invoke(ObjectMethodsFilter.java:44
)
        at $Proxy6.isDebugEnabled(Unknown Source)
        at 
org.apache.cocoon.components.thread.DefaultRunnableManager.dispose(DefaultRu
nnableManager.java:250)
        at 
org.apache.cocoon.components.thread.DefaultRunnableManagerTestCase.testExecu
teStringRunnablelonglong(DefaultRunnableManagerTestCase.java:1099)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at junit.framework.TestCase.runTest(TestCase.java:164)
        at junit.framework.TestCase.runBare(TestCase.java:130)
        at junit.framework.TestResult$1.protect(TestResult.java:106)
        at junit.framework.TestResult.runProtected(TestResult.java:124)
        at junit.framework.TestResult.run(TestResult.java:109)
        at junit.framework.TestCase.run(TestCase.java:120)
        at junit.framework.TestSuite.runTest(TestSuite.java:230)
        at junit.framework.TestSuite.run(TestSuite.java:225)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at 
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
        at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(Ab
stractDirectoryTestSuite.java:135)
        at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractD
irectoryTestSuite.java:122)
        at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireB
ooter.java:225)
        at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747
)
Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.786 sec
<<< FAILURE!

Re: thread.DefaultRunnableManagerTestCase failing

[Carsten Ziegeler <cz...@apache.org>]

Jorg Heymans wrote:
> Hi,
> 
> It seems that this testcase fails __sometimes__, is this known behaviour ?
> 
> 
I noticed this long time ago and I also think I notified this list :)
So, it seems
that this is the expected behaviour...but I guess its not the wanted
behaviour.



Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/