You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2012/05/22 15:28:42 UTC
Build failed in Jenkins: ESME #958
See <https://builds.apache.org/job/ESME/958/>
------------------------------------------
[...truncated 204 lines...]
INFO - Service request (POST) /api2/session returned 200, took 212 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 78 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 101 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds
INFO - Service request (POST) /api2/session returned 403, took 6 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds
INFO - Service request (GET) /api2/session returned 200, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds
INFO - Service request (GET) /api2/session returned 404, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds
INFO - Service request (DELETE) /api2/session returned 200, took 5 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 33 Milliseconds
INFO - Service request (DELETE) /api2/session returned 404, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (GET) /api2/users returned 200, took 13 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds
INFO - Service request (GET) /api2/users returned 403, took 7 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 60 Milliseconds
INFO - Service request (POST) /api2/users returned 200, took 585 Milliseconds
INFO - Service request (GET) /api2/users returned 200, took 7 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 59 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds
INFO - Service request (POST) /api2/users returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds
INFO - Service request (POST) /api2/users returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 58 Milliseconds
INFO - Service request (GET) /api2/users/18/tokens returned 200, took 13 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds
INFO - Service request (GET) /api2/users/2/tokens returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds
INFO - Service request (GET) /api2/users/2/tokens returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds
INFO - Service request (POST) /api2/users/19/tokens returned 200, took 6 Milliseconds
INFO - Service request (GET) /api2/users/19/tokens returned 200, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 228 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 241 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 80 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 134 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 16 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 31 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 399 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 158 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 35 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 144 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 52 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 26 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 6 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 30 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 18 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 3 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 2012 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 26 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 36 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 70 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 7 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 35 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 403, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 62 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 51 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 39 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 136 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 96 Milliseconds
INFO - Service request (GET) /api2/user/followees returned 200, took 9 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 32 Milliseconds
INFO - Service request (GET) /api2/user/followees returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 34 Milliseconds
INFO - Service request (POST) /api2/user/followees returned 200, took 45 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 33 Milliseconds
INFO - Service request (POST) /api2/user/followees returned 403, took 5 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 35 Milliseconds
INFO - Service request (GET) /api2/user/followers returned 200, took 9 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 38 Milliseconds
INFO - Service request (GET) /api2/user/followers returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 37 Milliseconds
INFO - Service request (GET) /api2/user/tracks returned 200, took 24 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 39 Milliseconds
INFO - Service request (GET) /api2/user/tracks returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 770 Milliseconds
INFO - Service request (POST) /api2/user/tracks returned 200, took 10 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 42 Milliseconds
INFO - Service request (POST) /api2/user/tracks returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 46 Milliseconds
INFO - Service request (POST) /api2/user/tracks returned 200, took 5 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/2 returned 200, took 27 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/1 returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (GET) /api2/user/actions returned 200, took 20 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (GET) /api2/user/actions returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (POST) /api2/user/actions returned 200, took 203 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 60 Milliseconds
INFO - Service request (POST) /api2/user/actions returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 26 Milliseconds
INFO - Service request (POST) /api2/user/actions returned 200, took 10 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 returned 200, took 31 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 427 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 56 Milliseconds
:12:203: '/' expected instead of ' '
^
INFO - Service request (GET) /api2//conversations/123 returned 200, took 20 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 50 Milliseconds
INFO - Service request (GET) /api2/conversations/1 returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 49 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 returned 404, took 6 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 36 Milliseconds
INFO - Service request (GET) /api2/pools returned 200, took 23 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 80 Milliseconds
INFO - Service request (GET) /api2/pools returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 295 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 7 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 142 Milliseconds
INFO - Service request (POST) /api2/pools returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 140 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 9 Milliseconds
INFO - Service request (POST) /api2/pools/3/users returned 403, took 16 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 31 Milliseconds
INFO - Service request (POST) /api2/pools/1/users returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages returned 204, took 9 Milliseconds
:12:203: '/' expected instead of ' '
^
INFO - Service request (POST) /api2/user/messages returned 200, took 63 Milliseconds
:12:203: '/' expected instead of ' '
^
INFO - Service request (GET) /api2/pools/4/messages returned 200, took 8 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 403, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 3 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 74 Milliseconds
INFO - Service request (GET) /api2/pools/5/messages returned 200, took 68 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 26 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 26 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 30 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 27 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 200, took 27 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 200, took 8 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/pools returned 403, took 5 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 204, took 4 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 27 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 200, took 11 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 109 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 7 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages returned 403, took 4 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 25 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 34 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 80 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 3 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 2011 Milliseconds
Tests run: 66, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 37.386 sec <<< FAILURE!
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.914 sec
Running org.apache.esme.AppTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.089 sec
Results :
Failed tests:
StatusNeg(org.apache.esme.api.ApiSpecs$):
Logout(org.apache.esme.api.ApiSpecs$):
LogoutNeg(org.apache.esme.api.ApiSpecs$):
SendMsg(org.apache.esme.api.ApiSpecs$):
SendMsgNeg(org.apache.esme.api.ApiSpecs$):
AddAction(org.apache.esme.api.ApiSpecs$):
AddActionNeg(org.apache.esme.api.ApiSpecs$):
SendMessageToken(org.apache.esme.api.ApiSpecs$):
AddPool(org.apache.esme.api.ApiSpecs$):
AddPoolNeg(org.apache.esme.api.ApiSpecs$):
with valid session(org.apache.esme.api.Api2Specs$):
Tests run: 97, Failures: 11, Errors: 0, Skipped: 0
[ERROR] There are test failures.
Please refer to <https://builds.apache.org/job/ESME/ws/server/target/surefire-reports> for the individual test results.
[JENKINS] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[esme-server] in [<https://builds.apache.org/job/ESME/ws/server/target/esme-server-apache-esme-1.4]>
[INFO] Processing war project
[INFO] Copying webapp resources[<https://builds.apache.org/job/ESME/ws/server/src/main/webapp]>
[INFO] Webapp assembled in[16979 msecs]
[INFO] Building war: <https://builds.apache.org/job/ESME/ws/server/target/esme-server-apache-esme-1.4.war>
[INFO] [install:install {execution: default-install}]
[INFO] Installing <https://builds.apache.org/job/ESME/ws/server/target/esme-server-apache-esme-1.4.war> to /export/home/hudson/hudson-slave/maven-repositories/0/org/apache/esme/esme-server/apache-esme-1.4/esme-server-apache-esme-1.4.war
[JENKINS] Archiving <https://builds.apache.org/job/ESME/ws/server/pom.xml> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2012-05-22_12-11-16/archive/org.apache.esme/esme-server/apache-esme-1.4/esme-server-apache-esme-1.4.pom
[JENKINS] Archiving <https://builds.apache.org/job/ESME/ws/server/target/esme-server-apache-esme-1.4.war> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2012-05-22_12-11-16/archive/org.apache.esme/esme-server/apache-esme-1.4/esme-server-apache-esme-1.4.war
Build timed out (after 70 minutes). Marking the build as failed.
Maven failed with error.
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to call isArchivingDisabled. Invalid object ID 5
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalStateException: Unable to call isArchivingDisabled. Invalid object ID 5
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:268)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:255)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 62 minutes 55 seconds
[INFO] Finished at: Tue May 22 13:22:06 GMT+00:00 2012
[INFO] Final Memory: 41M/332M
[INFO] ------------------------------------------------------------------------
channel stopped
[WARNINGS] Skipping publisher since build result is FAILURE