See <https://builds.apache.org/job/ESME/1319/>
------------------------------------------ [...truncated 169 lines...] INFO - Service request (GET) /twitter/statuses/public_timeline.xml returned 200, took 180 Milliseconds INFO - Service request (GET) /twitter/statuses/user_timeline.xml returned 200, took 82 Milliseconds INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200, took 120 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 3 Milliseconds INFO - Service request (POST) /twitter/friendships/create/twitter_user.xml returned 200, took 583 Milliseconds INFO - Service request (GET) /twitter/statuses/followers.xml returned 200, took 115 Milliseconds INFO - Service request (GET) /twitter/statuses/followers.xml returned 200, took 36 Milliseconds INFO - Service request (GET) /twitter/statuses/friends.xml returned 200, took 88 Milliseconds INFO - Service request (GET) /twitter/statuses/friends.xml returned 200, took 26 Milliseconds INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 44 Milliseconds INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200, took 25 Milliseconds INFO - Service request (POST) /twitter/statuses/update.xml returned 200, took 14 Milliseconds INFO - Service request (GET) /twitter/statuses/home_timeline.xml returned 200, took 33 Milliseconds INFO - Service request (GET) /twitter/statuses/public_timeline.xml returned 200, took 76 Milliseconds INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml returned 200, took 414 Milliseconds Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.321 sec Running org.apache.esme.api.Api2SpecsAsTest INFO - Service request (POST) /api2/session returned 200, took 218 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 28 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 42 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 176 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 32 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 39 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 51 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 42 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 41 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 84 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 77 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 24 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 23 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 23 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 58 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 73 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 49 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 (POST) /api2/session returned 200, took 29 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 60 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 75 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 145 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 142 Milliseconds INFO - Service request (POST) /api2/session returned 403, took 84 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 206 Milliseconds INFO - Service request (GET) /api2/session returned 200, took 122 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 36 Milliseconds INFO - Service request (GET) /api2/session returned 404, took 18 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds INFO - Service request (DELETE) /api2/session returned 200, took 6 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 34 Milliseconds INFO - Service request (DELETE) /api2/session returned 404, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 75 Milliseconds INFO - Service request (GET) /api2/users returned 200, took 294 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 70 Milliseconds INFO - Service request (GET) /api2/users returned 403, took 8 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 239 Milliseconds INFO - Service request (POST) /api2/users returned 200, took 534 Milliseconds INFO - Service request (GET) /api2/users returned 200, took 9 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 44 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 36 Milliseconds INFO - Service request (POST) /api2/users returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 94 Milliseconds INFO - Service request (POST) /api2/users returned 403, took 5 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 778 Milliseconds INFO - Service request (GET) /api2/users/18/tokens returned 200, took 102 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 37 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 36 Milliseconds INFO - Service request (GET) /api2/users/2/tokens returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds INFO - Service request (GET) /api2/users/2/tokens returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds INFO - Service request (POST) /api2/users/19/tokens returned 200, took 12 Milliseconds INFO - Service request (GET) /api2/users/19/tokens returned 200, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 37 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds INFO - Service request (POST) /api2/users/2/tokens returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 62 Milliseconds INFO - Service request (POST) /api2/users/2/tokens returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 381 Milliseconds INFO - Service request (GET) /api2/user/messages returned 200, took 144 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 59 Milliseconds INFO - Service request (GET) /api2/user/messages returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 36 Milliseconds INFO - Service request (GET) /api2/user/messages returned 204, took 68 Milliseconds INFO - Service request (GET) /api2/user/messages returned 204, took 2 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 26 Milliseconds INFO - Service request (GET) /api2/user/messages returned 200, took 399 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 103 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 31 Milliseconds INFO - Service request (GET) /api2/user/messages returned 200, took 75 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds INFO - Service request (GET) /api2/user/messages returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 20 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 23 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 1595 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 378 Milliseconds INFO - Service request (GET) /api2/user/messages returned 200, took 5 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 25 Milliseconds INFO - Service request (POST) /api2/user/messages returned 403, took 2 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 122 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 (POST) /api2/session returned 200, took 21 Milliseconds INFO - Service request (GET) /api2/user/followees returned 200, took 71 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds INFO - Service request (GET) /api2/user/followees returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 43 Milliseconds INFO - Service request (POST) /api2/user/followees returned 200, took 89 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds INFO - Service request (POST) /api2/user/followees returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 66 Milliseconds INFO - Service request (GET) /api2/user/followers returned 200, took 57 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 41 Milliseconds INFO - Service request (GET) /api2/user/followers returned 403, took 2 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 40 Milliseconds INFO - Service request (GET) /api2/user/tracks returned 200, took 70 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 34 Milliseconds INFO - Service request (POST) /api2/user/tracks returned 200, took 318 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 221 Milliseconds INFO - Service request (POST) /api2/user/tracks returned 403, took 2 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 76 Milliseconds INFO - Service request (POST) /api2/user/tracks returned 200, took 7 Milliseconds INFO - Service request (DELETE) /api2/user/tracks/2 returned 200, took 116 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds INFO - Service request (DELETE) /api2/user/tracks/1 returned 403, took 2 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds INFO - Service request (GET) /api2/user/actions returned 200, took 39 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds INFO - Service request (GET) /api2/user/actions returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 55 Milliseconds INFO - Service request (POST) /api2/user/actions returned 200, took 1931 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 21 Milliseconds INFO - Service request (POST) /api2/user/actions returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 22 Milliseconds INFO - Service request (POST) /api2/user/actions returned 200, took 10 Milliseconds INFO - Service request (DELETE) /api2/user/actions/2 returned 200, took 160 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 20 Milliseconds INFO - Service request (DELETE) /api2/user/actions/1 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 61 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 75 Milliseconds INFO - Service request (GET) /api2//conversations/123 returned 200, took 20 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 24 Milliseconds INFO - Service request (GET) /api2/conversations/1 returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 192 Milliseconds INFO - Service request (GET) /api2/conversations/10000 returned 404, took 12 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 87 Milliseconds INFO - Service request (GET) /api2/pools returned 200, took 877 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 113 Milliseconds INFO - Service request (GET) /api2/pools returned 403, took 2 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 68 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 8 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 25 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds INFO - Service request (POST) /api2/pools/3/users returned 403, took 226 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 333 Milliseconds INFO - Service request (POST) /api2/pools/1/users returned 403, took 2 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 27 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds INFO - Service request (GET) /api2/pools/4/messages returned 204, took 924 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 208 Milliseconds INFO - Service request (GET) /api2/pools/4/messages returned 200, took 47 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 217 Milliseconds INFO - Service request (GET) /api2/pools/1/messages returned 403, took 17 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 47 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 6 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 37 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 34 Milliseconds INFO - Service request (GET) /api2/pools/5/messages returned 200, took 1393 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 87 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 6 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 107 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 52 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 32 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 31 Milliseconds INFO - Service request (GET) /api2/pools/6/messages returned 200, took 55 Milliseconds INFO - Service request (GET) /api2/pools/6/messages returned 200, took 9 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 259 Milliseconds INFO - Service request (GET) /api2/pools/1/messages returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 36 Milliseconds INFO - Service request (POST) /api2/pools returned 403, took 53 Milliseconds INFO - Service request (GET) /api2/pools/6/messages returned 204, took 5 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 44 Milliseconds INFO - Service request (GET) /api2/pools/6/messages returned 200, took 167 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 38 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 68 Milliseconds INFO - Service request (POST) /api2/pools returned 200, took 8 Milliseconds INFO - Service request (GET) /api2/pools/7/messages returned 403, took 4 Milliseconds INFO - Service request (POST) /api2/user/messages returned 200, took 274 Milliseconds INFO - Service request (GET) /api2/pools/7/messages returned 403, took 3 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 77 Milliseconds INFO - Service request (GET) /api2/pools/1/messages returned 403, took 6 Milliseconds INFO - Service request (POST) /api2/session returned 200, took 80 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: 62.429 sec <<< FAILURE! Running org.apache.esme.actor.PopStatsActorSpecsAsTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.666 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[60832 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/1/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-06-03_12-23-26/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-06-03_12-23-26/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. [WARNINGS] Skipping publisher since build result is FAILURE
