strange. i tried to isolate the problem by disabling all integration tests by 
added junit @Ignore annotation to them.
the HistoryTest IT runs then fine.
i startet adding/removing more integration tests and sometims it succeeds, 
sometimes not. perhaps a racing condition, or a cleanup issue of the 
integration tests.

if it fails it takes a long time executing this step "Starting job queue test":

...
16.10.2013 13:23:27.352 *INFO* [Thread-102] 
org.apache.sling.event.impl.jobs.TopologyCapabilities Detected capabilities of 
86db438e-86fa-43b2-85c2-62d22a12db6b : 
/,sling/test/history,sling/webconsole/test
16.10.2013 13:23:27.352 *INFO* [Thread-102] 
PAXEXAM-PROBE-914abd18-50d6-448f-82ca-29f27441a4cc Service [99] ServiceEvent 
REGISTERED
16.10.2013 13:23:29.342 *INFO* [Apache Sling Job Background Loader] 
org.apache.sling.event Service [QueueMBean for queue test,100] ServiceEvent 
REGISTERED
16.10.2013 13:23:29.342 *INFO* [Apache Sling Job Queue test] 
org.apache.sling.event.impl.jobs.queues.OrderedJobQueue.test Starting job queue 
test

>> it hangs here for several minutes <<

16.10.2013 13:28:27.364 *INFO* [CM Event Dispatcher (Fire ConfigurationEvent: 
pid=org.apache.sling.event.jobs.QueueConfiguration.2be31a75-f846-4e17-a1b9-8482c5fcaed2)]
 org.apache.sling.event Service 
[org.apache.sling.event.jobs.QueueConfiguration.2be31a75-f846-4e17-a1b9-8482c5fcaed2,98]
 ServiceEvent UNREGISTERING
16.10.2013 13:28:27.364 *INFO* [main] 
PAXEXAM-PROBE-914abd18-50d6-448f-82ca-29f27441a4cc BundleEvent STOPPING
16.10.2013 13:28:27.364 *INFO* [main] 
PAXEXAM-PROBE-914abd18-50d6-448f-82ca-29f27441a4cc Service [73] ServiceEvent 
UNREGISTERING
...

the failsafe report contains only this:

-------------------------------------------------------------------------------
Test set: org.apache.sling.event.it.HistoryTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 305.173 sec <<< 
FAILURE!
testHistory(org.apache.sling.event.it.HistoryTest)  Time elapsed: 305.163 sec  
<<< ERROR!
java.lang.Exception: test timed out after 300000 milliseconds
        at java.lang.Thread.sleep(Native Method)
        at 
org.apache.sling.event.it.AbstractJobHandlingTest.sleep(AbstractJobHandlingTest.java:160)
        at 
org.apache.sling.event.it.HistoryTest.testHistory(HistoryTest.java:118)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
        at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
        at 
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)


stefan

>-----Original Message-----
>From: Carsten Ziegeler [mailto:cziege...@apache.org]
>Sent: Wednesday, October 16, 2013 12:08 PM
>To: dev@sling.apache.org
>Subject: Re: failure running sling.extensions.event unit/integraiton
>tests on windows?
>
>Hi,
>
>the tests run fine on my machine - it seems that in your case the loop
>waits forever to get 10 finished jobs in the history.
>Do you see any exception in the log output?
>
>Carsten

Reply via email to