It goes further, but just want to point out I'm now see this error:
Thanks
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.tuscany.container.groovy.ScriptInvokeTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.953
sec
Running org.apache.tuscany.container.groovy.PropertyTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062
sec
Running org.apache.tuscany.container.groovy.WireTestCase
Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.125
sec <<< FAILURE!
testTargetInvocation(org.apache.tuscany.container.groovy.WireTestCase)
Time elapsed: 0.016 sec <<< ERROR!
java.lang.reflect.InvocationTargetException
at
org.apache.tuscany.container.groovy.GroovyInvoker.invokeTarget(GroovyInvoker.java:63)
at
org.apache.tuscany.container.groovy.WireTestCase.testTargetInvocation(WireTestCase.java:131)
testTargetWireInvocation(org.apache.tuscany.container.groovy.WireTestCase)
Time elapsed: 0.015 sec <<< ERROR!
java.lang.NullPointerException: Cannot invoke method greet() on null
object
at org.codehaus.groovy.runtime.Invoker.invokeMethod(Invoker.java:129)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:104)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethod(ScriptBytecodeAdapter.java:85)
at Foo.greet(script1153755178854.groovy:1)
at gjdk.Foo_GroovyReflector.invoke(Unknown Source)
at groovy.lang.MetaMethod.invoke(MetaMethod.java:111)
at
org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassHelper.java:636)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:345)
at gjdk.groovy.lang.MetaClassImpl_GroovyReflector.invoke(Unknown
Source)
at groovy.lang.MetaMethod.invoke(MetaMethod.java:111)
at
org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassHelper.java:636)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:345)
at org.codehaus.groovy.runtime.Invoker.invokeMethod(Invoker.java:144)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:104)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethod(ScriptBytecodeAdapter.java:85)
at Foo.invokeMethod(script1153755178854.groovy)
at
org.apache.tuscany.container.groovy.GroovyInvoker.invokeTarget(GroovyInvoker.java:61)
at
org.apache.tuscany.container.groovy.GroovyInvoker.invoke(GroovyInvoker.java:69)
at
org.apache.tuscany.core.wire.InvokerInterceptor.invoke(InvokerInterceptor.java:39)
at
org.apache.tuscany.core.wire.jdk.JDKInboundInvocationHandler.invoke(JDKInboundInvocationHandler.java:102)
at $Proxy2.greet(Unknown Source)
at
org.apache.tuscany.container.groovy.WireTestCase.testTargetWireInvocation(WireTestCase.java:161)
Running org.apache.tuscany.container.groovy.ImplementationLoaderTestCase
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.344
sec
Results :
Tests run: 8, Failures: 0, Errors: 2, Skipped: 0
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] There are test failures.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 39 seconds
[INFO] Finished at: Mon Jul 24 11:32:59 EDT 2006
[INFO] Final Memory: 35M/254M
[INFO]
------------------------------------------------------------------------
Jim Marino wrote:
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.ThreadPoolW
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.ThreadPoolWo
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
