O.K. the easiest thing I think to do is what Jeremy mentioned and
stub out the Executor since this is going to cause issues on
different machines. I've commented out the test cases for now and
I'll go back in later and stub out the Executor.
Jim
On Jul 24, 2006, at 8:15 AM, Ignacio Silva-Lepe wrote:
I was seeing a similar error as Rick, I updated and picked up the
fix and now I see the following error, after which the build hangs
(suspecting a deadlock now):
[surefire] Running
org.apache.tuscany.core.services.work.jsr237.Jsr237WorkSchedu
lerTestCase
[surefire] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.01
sec
[surefire]
Exception in thread "pool-8-thread-1" java.lang.AssertionError:
Unexpected method call workStarted
(org.apache.tuscany.core.services.work.jsr23
[EMAIL PROTECTED]):
workAccepted(isA(commonj.work.WorkEvent)): expected: 1, actual: 0
at org.easymock.internal.MockInvocationHandler.invoke
(MockInvocationHand
ler.java:29)
at org.easymock.internal.ObjectMethodsFilter.invoke
(ObjectMethodsFilter.
java:45)
at $Proxy50.workStarted(Unknown Source)
at
org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo
rkManager.workStarted(ThreadPoolWorkManager.java:140)
at
org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo
rkManager.access$100(ThreadPoolWorkManager.java:45)
at
org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo
rkManager$DecoratingWork.run(ThreadPoolWorkManager.java:201)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExec
utor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor
.java:675)
at java.lang.Thread.run(Thread.java:595)
----- Original Message ----- From: "Jim Marino"
<[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Monday, July 24, 2006 11:00 AM
Subject: Re: Java core test case failures?
Yea it is. I just checked in a fix. Please let me know if it works
on your machine, Rick.
Jim
On Jul 24, 2006, at 7:48 AM, Jeremy Boynes wrote:
On Jul 24, 2006, at 7:30 AM, Rick wrote:
testSchedule
(org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoo
lW orkManagerTestCase) Time elapsed: 0 sec <<< ERROR!
java.lang.AssertionError:
Expectation failure on verify:
run(): expected: 1, actual: 0
at org.easymock.internal.MocksControl.verify
(MocksControl.java:71)
at org.easymock.EasyMock.verify(EasyMock.java:1306)
at
org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPool
Wo rkManagerTestCase.testSchedule
(ThreadPoolWorkManagerTestCase.java:25)
This looks like a basic race condition in the testcase. Perhaps
we should add a constructor to ThreadPoolWorkManager that allows
the Executor to be mocked.
--
Jeremy
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
