See <https://builds.apache.org/job/ESME/1306/>
------------------------------------------ [...truncated 195 lines...] INFO - Service request (POST) /api2/session returned 200, took 30 Milliseconds INFO - Service request (GET) /api2/session returned 404, took 6 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 28 Milliseconds INFO - Service request (DELETE) /api2/session returned 200, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds INFO - Service request (DELETE) /api2/session returned 404, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 30 Milliseconds INFO - Service request (GET) /api2/users returned 200, took 13 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 27 Milliseconds INFO - Service request (GET) /api2/users returned 403, took 9 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 26 Milliseconds INFO - Service request (POST) /api2/users returned 200, took 169 Milliseconds INFO - Service request (GET) /api2/users returned 200, took 8 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 27 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds INFO - Service request (POST) /api2/users returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 25 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 (GET) /api2/users/16/tokens returned 200, took 12 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 33 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 63 Milliseconds INFO - Service request (GET) /api2/users/2/tokens returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 27 Milliseconds INFO - Service request (GET) /api2/users/2/tokens returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 34 Milliseconds INFO - Service request (POST) /api2/users/17/tokens returned 200, took 11 Milliseconds INFO - Service request (GET) /api2/users/17/tokens returned 200, took 5 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 88 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds INFO - Service request (POST) /api2/users/2/tokens returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds INFO - Service request (POST) /api2/users/2/tokens returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 42 Milliseconds INFO - Service request (GET) /api2/user/messages returned 200, took 18 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds INFO - Service request (GET) /api2/user/messages returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 23 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 23 Milliseconds INFO - Service request (GET) /api2/user/messages returned 200, took 41 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 31 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 (POST) /api2/user/messages returned 200, took 25 Milliseconds INFO - Service request (GET) /api2/user/messages returned 200, took 9 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 54 Milliseconds INFO - Service request (GET) /api2/user/messages returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 54 Milliseconds INFO - Service request (GET) /api2/user/messages returned 204, took 3 Milliseconds INFO - Service request (GET) /api2/user/messages returned 204, took 2011 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 344 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 39 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 61 Milliseconds INFO - Service request (GET) /api2/user/messages returned 200, took 5 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 27 Milliseconds INFO - Service request (POST) /api2/user/messages returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 71 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 28 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds INFO - Service request (GET) /api2/user/followees returned 200, took 19 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds INFO - Service request (GET) /api2/user/followees returned 403, took 2 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 30 Milliseconds INFO - Service request (POST) /api2/user/followees returned 200, took 134 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds INFO - Service request (POST) /api2/user/followees returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 26 Milliseconds INFO - Service request (GET) /api2/user/followers returned 200, took 8 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 95 Milliseconds INFO - Service request (GET) /api2/user/followers returned 403, took 2 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds INFO - Service request (GET) /api2/user/tracks returned 200, took 19 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 29 Milliseconds INFO - Service request (GET) /api2/user/tracks returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 33 Milliseconds INFO - Service request (POST) /api2/user/tracks returned 200, took 15 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 53 Milliseconds INFO - Service request (POST) /api2/user/tracks returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 37 Milliseconds INFO - Service request (POST) /api2/user/tracks returned 200, took 6 Milliseconds INFO - Service request (DELETE) /api2/user/tracks/2 returned 200, took 37 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 56 Milliseconds INFO - Service request (DELETE) /api2/user/tracks/1 returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 36 Milliseconds INFO - Service request (GET) /api2/user/actions returned 200, took 26 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 39 Milliseconds INFO - Service request (GET) /api2/user/actions returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 107 Milliseconds INFO - Service request (POST) /api2/user/actions returned 200, took 185 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 65 Milliseconds INFO - Service request (POST) /api2/user/actions returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 35 Milliseconds INFO - Service request (POST) /api2/user/actions returned 200, took 16 Milliseconds INFO - Service request (DELETE) /api2/user/actions/2 returned 200, took 36 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 33 Milliseconds INFO - Service request (DELETE) /api2/user/actions/1 returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 34 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 33 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 121 Milliseconds INFO - Service request (GET) /api2//conversations/116 returned 200, took 25 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 78 Milliseconds INFO - Service request (GET) /api2/conversations/1 returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 57 Milliseconds INFO - Service request (GET) /api2/conversations/10000 returned 404, took 6 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 95 Milliseconds INFO - Service request (GET) /api2/pools returned 200, took 31 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 33 Milliseconds INFO - Service request (GET) /api2/pools returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 34 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 10 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 35 Milliseconds INFO - Service request (POST) /api2/pools returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 35 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 9 Milliseconds INFO - Service request (POST) /api2/pools/3/users returned 403, took 20 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 41 Milliseconds INFO - Service request (POST) /api2/pools/1/users returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 35 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 8 Milliseconds INFO - Service request (GET) /api2/pools/4/messages returned 204, took 10 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 47 Milliseconds INFO - Service request (GET) /api2/pools/4/messages returned 200, took 9 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 44 Milliseconds INFO - Service request (GET) /api2/pools/1/messages returned 403, took 6 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 34 Milliseconds INFO - Service request (GET) /api2/pools/1/messages returned 204, took 813 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 24 Milliseconds INFO - Service request (GET) /api2/pools/5/messages returned 200, took 70 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 159 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 91 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 155 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 156 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 62 Milliseconds INFO - Service request (GET) /api2/pools/6/messages returned 200, took 29 Milliseconds INFO - Service request (GET) /api2/pools/6/messages returned 200, took 9 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 180 Milliseconds INFO - Service request (GET) /api2/pools/1/messages returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 18 Milliseconds INFO - Service request (POST) /api2/pools returned 403, took 5 Milliseconds INFO - Service request (GET) /api2/pools/6/messages returned 204, took 2 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 24 Milliseconds INFO - Service request (GET) /api2/pools/6/messages returned 200, took 9 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/pools returned 200, took 6 Milliseconds INFO - Service request (GET) /api2/pools/7/messages returned 403, took 3 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 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 4 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: 36.537 sec <<< FAILURE! Running org.apache.esme.api.TwitterAPISpecsAsTest INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 36 Milliseconds INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 5 Milliseconds INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 2 Milliseconds INFO - Service request (GET) /twitter/statuses/public_timeline.xml returned 200, took 67 Milliseconds INFO - Service request (GET) /twitter/statuses/user_timeline.xml returned 200, took 28 Milliseconds INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200, took 39 Milliseconds INFO - Service request (GET) /twitter/statuses/user_timeline.xml returned 200, took 4 Milliseconds INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200, took 2 Milliseconds INFO - Service request (POST) /twitter/friendships/create/twitter_user.xml returned 200, took 41 Milliseconds INFO - Service request (GET) /twitter/statuses/followers.xml returned 200, took 17 Milliseconds INFO - Service request (GET) /twitter/statuses/followers.xml returned 200, took 5 Milliseconds INFO - Service request (GET) /twitter/statuses/friends.xml returned 200, took 14 Milliseconds INFO - Service request (GET) /twitter/statuses/friends.xml returned 200, took 7 Milliseconds INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 8 Milliseconds INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200, took 21 Milliseconds INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 9 Milliseconds INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200, took 35 Milliseconds INFO - Service request (GET) /twitter/statuses/public_timeline.xml returned 200, took 51 Milliseconds INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml returned 200, took 54 Milliseconds Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.319 sec Running org.apache.esme.AppTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.esme.actor.PopStatsActorSpecsAsTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.057 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[2252 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/2013-05-21_12-33-09/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/2013-05-21_12-33-09/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. [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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) [INFO] ------------------------------------------------------------------------ [INFO] Total time: 52 minutes 55 seconds [INFO] Finished at: Tue May 21 13:30:58 GMT+00:00 2013 [INFO] Final Memory: 40M/330M [INFO] ------------------------------------------------------------------------ Maven failed with error. channel stopped [WARNINGS] Skipping publisher since build result is FAILURE
