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/12/18 15:55:24 UTC
Build failed in Jenkins: ESME #1160
See <https://builds.apache.org/job/ESME/1160/>
------------------------------------------
[...truncated 192 lines...]
INFO - Service request (POST) /api2/session returned 200, took 43 Milliseconds
INFO - Service request (POST) /api2/session returned 403, took 6 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 170 Milliseconds
INFO - Service request (GET) /api2/session returned 200, took 6 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 79 Milliseconds
INFO - Service request (GET) /api2/session returned 404, took 5 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 528 Milliseconds
INFO - Service request (DELETE) /api2/session returned 200, took 6 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 79 Milliseconds
INFO - Service request (DELETE) /api2/session returned 404, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 79 Milliseconds
INFO - Service request (GET) /api2/users returned 200, took 11 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 53 Milliseconds
INFO - Service request (GET) /api2/users returned 403, took 7 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 246 Milliseconds
INFO - Service request (POST) /api2/users returned 200, took 470 Milliseconds
INFO - Service request (GET) /api2/users returned 200, took 5 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 54 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 51 Milliseconds
INFO - Service request (POST) /api2/users returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 121 Milliseconds
INFO - Service request (POST) /api2/users returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 34 Milliseconds
INFO - Service request (GET) /api2/users/5/tokens returned 200, took 16 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 92 Milliseconds
INFO - Service request (GET) /api2/users/4/tokens returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 44 Milliseconds
INFO - Service request (GET) /api2/users/4/tokens returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 88 Milliseconds
INFO - Service request (POST) /api2/users/6/tokens returned 200, took 9 Milliseconds
INFO - Service request (GET) /api2/users/6/tokens returned 200, took 6 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 267 Milliseconds
INFO - Service request (POST) /api2/users/4/tokens returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 28 Milliseconds
INFO - Service request (POST) /api2/users/4/tokens returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 49 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 16 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 109 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 4 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 37 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 213 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 6 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 2 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 204, took 2011 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 33 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 70 Milliseconds
INFO - Service request (GET) /api2/user/messages returned 200, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 43 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 33 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 199 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 71 Milliseconds
INFO - Service request (GET) /api2/user/followees returned 200, took 8 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 215 Milliseconds
INFO - Service request (GET) /api2/user/followees returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 35 Milliseconds
INFO - Service request (POST) /api2/user/followees returned 200, took 46 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 35 Milliseconds
INFO - Service request (POST) /api2/user/followees returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 74 Milliseconds
INFO - Service request (GET) /api2/user/followers returned 200, took 8 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 60 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 23 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 731 Milliseconds
INFO - Service request (GET) /api2/user/tracks returned 403, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 34 Milliseconds
INFO - Service request (POST) /api2/user/tracks returned 200, took 13 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 33 Milliseconds
INFO - Service request (POST) /api2/user/tracks returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 36 Milliseconds
INFO - Service request (POST) /api2/user/tracks returned 200, took 7 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/2 returned 200, took 34 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 251 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/1 returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 73 Milliseconds
INFO - Service request (GET) /api2/user/actions returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (GET) /api2/user/actions returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 35 Milliseconds
INFO - Service request (POST) /api2/user/actions returned 200, took 1285 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 79 Milliseconds
INFO - Service request (POST) /api2/user/actions returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 152 Milliseconds
INFO - Service request (POST) /api2/user/actions returned 200, took 11 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 returned 200, took 28 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 120 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 returned 403, took 6 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 95 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 105 Milliseconds
:12:203: '/' expected instead of ' '
^
INFO - Service request (POST) /api2/user/messages returned 200, took 882 Milliseconds
INFO - Service request (GET) /api2//conversations/99 returned 200, took 25 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds
INFO - Service request (GET) /api2/conversations/1 returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 returned 404, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (GET) /api2/pools returned 200, took 21 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 79 Milliseconds
INFO - Service request (GET) /api2/pools returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 18 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 7 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 29 Milliseconds
INFO - Service request (POST) /api2/pools returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 39 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds
INFO - Service request (POST) /api2/pools/3/users returned 403, took 15 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 27 Milliseconds
INFO - Service request (POST) /api2/pools/1/users returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 19 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages returned 204, took 8 Milliseconds
:12:203: '/' expected instead of ' '
^
INFO - Service request (POST) /api2/user/messages returned 200, took 26 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages returned 200, took 7 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 19 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 403, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 4 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 204, took 2 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 130 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 22 Milliseconds
:12:203: '/' expected instead of ' '
^
INFO - Service request (GET) /api2/pools/5/messages returned 200, took 396 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 74 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 8 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 52 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 75 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 253 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 115 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 14 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 100 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 403, took 4 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 53 Milliseconds
INFO - Service request (POST) /api2/pools returned 403, took 43 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 204, took 4 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 587 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages returned 200, took 9 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 17 Milliseconds
INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages returned 403, took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages returned 200, took 26 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages returned 403, took 3 Milliseconds
INFO - Service request (POST) /api2/session returned 200, took 111 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: 45.982 sec <<< FAILURE!
Running org.apache.esme.api.ApiSpecsAsTest
INFO - Service request (POST) /api/login returned 200, took 109 Milliseconds
INFO - Service request (GET) /api/status returned 200, took 4 Milliseconds
INFO - Service request (GET) /api/status returned 200, took 2 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 3 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 3 Milliseconds
INFO - Service request (GET) /api/status returned 200, took 2 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 22 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 18 Milliseconds
INFO - Service request (GET) /api/logout returned 200, took 3 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 18 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 19 Milliseconds
INFO - Service request (POST) /api/send_msg returned 200, took 3 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 40 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 18 Milliseconds
INFO - Service request (POST) /api/add_action returned 200, took 12 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 20 Milliseconds
INFO - Service request (POST) /api/send_msg returned 200, took 21 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 26 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt8787 returned 200, took 4 Milliseconds
INFO - Service request (POST) /api/login returned 200, took 19 Milliseconds
INFO - Service request (POST) /api/send_msg returned 404, took 76 Milliseconds
INFO - Service request (POST) /api/send_msg returned 200, took 2 Milliseconds
Tests run: 14, Failures: 10, Errors: 0, Skipped: 0, Time elapsed: 5.277 sec <<< FAILURE!
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.051 sec
Results :
Failed tests:
with valid session(org.apache.esme.api.Api2Specs$):
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$):
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.
[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:269)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256)
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:326)
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: 36 minutes 22 seconds
[INFO] Finished at: Tue Dec 18 14:05:41 GMT+00:00 2012
[INFO] Final Memory: 38M/336M
[INFO] ------------------------------------------------------------------------
channel stopped
[WARNINGS] Skipping publisher since build result is FAILURE