Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Carsten Ziegeler
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


2013/10/15 Stefan Seifert sseif...@pro-vision.de

 running win7 64bit, java 1.7.0_17, maven 3.0.5

 any idea why this integration tests for sling event module fails when
 building with mvn clean install?
 i assume they run on other platforms?

 
 Results :

 Tests in error:
   testHistory(org.apache.sling.event.it.HistoryTest): test timed out after
 30 milliseconds

 Tests run: 18, Failures: 0, Errors: 1, Skipped: 0
 

 the other integration tests are running, but take quite a lot of time to
 complete.

 stefan




-- 
Carsten Ziegeler
cziege...@apache.org


RE: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Stefan Seifert
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 30 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


Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Bertrand Delacretaz
On Tue, Oct 15, 2013 at 10:30 PM, Stefan Seifert sseif...@pro-vision.de wrote:
 ...running win7 64bit, java 1.7.0_17, maven 3.0.5

 any idea why this integration tests for sling event module fails when 
 building with mvn clean install?
 i assume they run on other platforms?...

Yes, they work for me (though integration tests take a lot of time,
total time 8 minutes in a debian VM on a 3-years old macbook), java
version 1.7.0_40, Debian 4.6.3-14.

And also at
https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.event/

-Bertrand


Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Carsten Ziegeler
Yes, it seems to hang at that point as it doesn't get any jobs - I guess
the difference between windows and other machines is the order in which
test cases are executed. So it must be some previous test which does not
clean up correctly. Can you please find out from the logs which tests are
run before the HistoryTest?

Carsten


2013/10/16 Stefan Seifert sseif...@pro-vision.de

 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 30 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




-- 
Carsten Ziegeler
cziege...@apache.org


RE: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Stefan Seifert
i was able to reproduce it in 2 of 3 tries with only two integration tests 
activated:
- ClassloadingTest
- HistoryTest

running historytest or ClassloadingTest standalone worked.
running both (i assume ClassloadingTest did run first) did not work in 2 of 3 
tries.

stefan

-Original Message-
From: Carsten Ziegeler [mailto:cziege...@apache.org]
Sent: Wednesday, October 16, 2013 4:50 PM
To: dev@sling.apache.org
Subject: Re: failure running sling.extensions.event unit/integraiton
tests on windows?

Yes, it seems to hang at that point as it doesn't get any jobs - I
guess
the difference between windows and other machines is the order in
which
test cases are executed. So it must be some previous test which does
not
clean up correctly. Can you please find out from the logs which tests
are
run before the HistoryTest?

Carsten


Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Robert Munteanu
On Wed, Oct 16, 2013 at 5:55 PM, Stefan Seifert sseif...@pro-vision.de wrote:
 i was able to reproduce it in 2 of 3 tries with only two integration tests 
 activated:
 - ClassloadingTest
 - HistoryTest

 running historytest or ClassloadingTest standalone worked.
 running both (i assume ClassloadingTest did run first) did not work in 2 of 3 
 tries.

Seems to be related to

SLING-2969: IT failure: ClassloadingTest.testSimpleClassloading fails
intermitently
https://issues.apache.org/jira/browse/SLING-2969

Robert


 stefan

-Original Message-
From: Carsten Ziegeler [mailto:cziege...@apache.org]
Sent: Wednesday, October 16, 2013 4:50 PM
To: dev@sling.apache.org
Subject: Re: failure running sling.extensions.event unit/integraiton
tests on windows?

Yes, it seems to hang at that point as it doesn't get any jobs - I
guess
the difference between windows and other machines is the order in
which
test cases are executed. So it must be some previous test which does
not
clean up correctly. Can you please find out from the logs which tests
are
run before the HistoryTest?

Carsten



-- 
Sent from my (old) computer


Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Carsten Ziegeler
I just added an additional ine to the Classloading test removing stale
jobs, but I don't think that's the problem :( Apart from that I can't see
anything spurious in the test

Carsten


2013/10/16 Robert Munteanu rob...@lmn.ro

 On Wed, Oct 16, 2013 at 5:55 PM, Stefan Seifert sseif...@pro-vision.de
 wrote:
  i was able to reproduce it in 2 of 3 tries with only two integration
 tests activated:
  - ClassloadingTest
  - HistoryTest
 
  running historytest or ClassloadingTest standalone worked.
  running both (i assume ClassloadingTest did run first) did not work in 2
 of 3 tries.

 Seems to be related to

 SLING-2969: IT failure: ClassloadingTest.testSimpleClassloading fails
 intermitently
 https://issues.apache.org/jira/browse/SLING-2969

 Robert

 
  stefan
 
 -Original Message-
 From: Carsten Ziegeler [mailto:cziege...@apache.org]
 Sent: Wednesday, October 16, 2013 4:50 PM
 To: dev@sling.apache.org
 Subject: Re: failure running sling.extensions.event unit/integraiton
 tests on windows?
 
 Yes, it seems to hang at that point as it doesn't get any jobs - I
 guess
 the difference between windows and other machines is the order in
 which
 test cases are executed. So it must be some previous test which does
 not
 clean up correctly. Can you please find out from the logs which tests
 are
 run before the HistoryTest?
 
 Carsten



 --
 Sent from my (old) computer




-- 
Carsten Ziegeler
cziege...@apache.org