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 Hudson Server <hu...@hudson.apache.org> on 2011/01/16 13:43:01 UTC
Build failed in Hudson: ESME #472
See <https://hudson.apache.org/hudson/job/ESME/472/>
------------------------------------------
[...truncated 210 lines...]
INFO - Service request (GET) /api2/users/2/tokens took 3 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/users/4/tokens took 7 Milliseconds
INFO - Service request (GET) /api2/users/4/tokens took 6 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens took 3 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens took 3 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/user/messages took 644 Milliseconds
INFO - Service request (GET) /api2/user/messages took 36 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/user/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (GET) /api2/user/messages took 5 Milliseconds
INFO - Service request (GET) /api2/user/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (GET) /api2/user/messages took 40 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/user/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/user/messages took 36 Milliseconds
INFO - Service request (GET) /api2/user/messages took 731 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/user/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/user/messages took 4 Milliseconds
INFO - Service request (GET) /api2/user/messages took 2011 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/pools took 47 Milliseconds
INFO - Service request (POST) /api2/user/messages took 73 Milliseconds
INFO - Service request (GET) /api2/user/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 42 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/user/messages took 46 Milliseconds
INFO - Service request (POST) /api2/session took 206 Milliseconds
INFO - Service request (GET) /api2/user/followees took 15 Milliseconds
INFO - Service request (POST) /api2/session took 13 Milliseconds
INFO - Service request (GET) /api2/user/followees took 2 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/followees took 192 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/followees took 2 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/followers took 8 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/followers took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 19 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 3 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 10 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 3 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 6 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/2 took 27 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/actions took 20 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/actions took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/actions took 53 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/actions took 2 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/actions took 12 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 took 1073 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 took 3 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/messages took 727 Milliseconds
INFO - Service request (POST) /api2/user/messages took 120 Milliseconds
INFO - Service request (GET) /api2/conversations/9 took 21 Milliseconds
INFO - Service request (POST) /api2/session took 9 Milliseconds
INFO - Service request (GET) /api2/conversations/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 took 5 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/pools took 22 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/pools took 2 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/pools took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (POST) /api2/pools/3/users took 32 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools/1/users took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 46 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (POST) /api2/user/messages took 147 Milliseconds
INFO - Service request (GET) /api2/pools/5/messages took 65 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 43 Milliseconds
INFO - Service request (POST) /api2/user/messages took 56 Milliseconds
INFO - Service request (POST) /api2/user/messages took 36 Milliseconds
INFO - Service request (POST) /api2/user/messages took 29 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 33 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/pools took 5 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 3 Milliseconds
INFO - Service request (POST) /api2/user/messages took 97 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 9 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 3 Milliseconds
INFO - Service request (POST) /api2/user/messages took 167 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 2 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 2011 Milliseconds
Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 35.807 sec
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.059 sec
Running org.apache.esme.api.ApiSpecsAsTest
INFO - Service request (POST) /api/login took 23 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (POST) /api/login took 3 Milliseconds
INFO - Service request (POST) /api/login took 3 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 13 Milliseconds
INFO - Service request (GET) /api/logout took 6 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 8 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (GET) /api/logout took 5 Milliseconds
INFO - Service request (POST) /api/login took 8 Milliseconds
INFO - Service request (GET) /api/logout took 4 Milliseconds
INFO - Service request (GET) /api/logout took 4 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (POST) /api/send_msg took 6 Milliseconds
INFO - Service request (POST) /api/send_msg took 4 Milliseconds
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (POST) /api/add_action took 20 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 11 Milliseconds
INFO - Service request (POST) /api/add_action took 16 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt took 7 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/send_msg took 12 Milliseconds
Full(<esme_api success="true"><xml:group></xml:group></esme_api>)
INFO - Service request (POST) /api/login took 12 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt87 took 11 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt8787 took 3 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (POST) /api/add_pool took 16 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
Full(<esme_api msg="message parameter is missing" success="false"><xml:group></xml:group></esme_api>)
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.392 sec
Running org.apache.esme.api.TwitterAPISpecsAsTest
INFO - Service request (POST) /twitter/statuses/update.xml took 36 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 5 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 74 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 29 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 39 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 2 Milliseconds
INFO - Service request (POST) /twitter/friendships/create/twitter_user.xml took 75 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 18 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 4 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 14 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 8 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 7 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 24 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 7 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 37 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 52 Milliseconds
INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml took 56 Milliseconds
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.49 sec
Results :
Tests run: 118, Failures: 0, Errors: 0, Skipped: 0
[HUDSON] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[esme-server] in [<https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2]>
[INFO] Processing war project
[INFO] Copying webapp resources[<https://hudson.apache.org/hudson/job/ESME/ws/server/src/main/webapp]>
[INFO] Webapp assembled in[5969 msecs]
[INFO] Building war: <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war>
[INFO] [install:install {execution: default-install}]
[INFO] Installing <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war> to /export/home/hudson/.m2/repository/org/apache/esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war
[HUDSON] Archiving <https://hudson.apache.org/hudson/job/ESME/ws/server/pom.xml> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2011-01-16_12-15-36/archive/org.apache.esme/esme-server/apache-esme-1.2/pom.xml
[HUDSON] Archiving <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2011-01-16_12-15-36/archive/org.apache.esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war
Build timed out. Aborting
[WARNINGS] Skipping publisher since build result is FAILURE
Skipping Cobertura coverage report as build was not SUCCESS or better ...
Build failed in Hudson: ESME #473
Posted by Apache Hudson Server <hu...@hudson.apache.org>.
See <https://hudson.apache.org/hudson/job/ESME/473/changes>
Changes:
[esjewett] [ESME-322] Fix scripts not loading under Tomcat
Patch by Eric Christeson
------------------------------------------
[...truncated 216 lines...]
INFO - Service request (GET) /api2/users/2/tokens took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/users/4/tokens took 10 Milliseconds
INFO - Service request (GET) /api2/users/4/tokens took 8 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens took 2 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/user/messages took 85 Milliseconds
INFO - Service request (GET) /api2/user/messages took 21 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/user/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (GET) /api2/user/messages took 6 Milliseconds
INFO - Service request (GET) /api2/user/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/user/messages took 40 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/user/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/user/messages took 38 Milliseconds
INFO - Service request (GET) /api2/user/messages took 9 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/user/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/user/messages took 3 Milliseconds
INFO - Service request (GET) /api2/user/messages took 2010 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/pools took 50 Milliseconds
INFO - Service request (POST) /api2/user/messages took 96 Milliseconds
INFO - Service request (GET) /api2/user/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 43 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 332 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/followees took 19 Milliseconds
INFO - Service request (POST) /api2/session took 13 Milliseconds
INFO - Service request (GET) /api2/user/followees took 2 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/user/followees took 38 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/followees took 2 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/followers took 9 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/followers took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 20 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 3 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 12 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 3 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 7 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/2 took 29 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/1 took 3 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/actions took 20 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/actions took 3 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/actions took 480 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/actions took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/actions took 11 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 took 29 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/user/messages took 22 Milliseconds
INFO - Service request (POST) /api2/user/messages took 68 Milliseconds
INFO - Service request (GET) /api2/conversations/9 took 20 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (GET) /api2/conversations/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 took 7 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/pools took 24 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/pools took 3 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/pools took 2 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/pools/3/users took 34 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools/1/users took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 9 Milliseconds
INFO - Service request (POST) /api2/user/messages took 28 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 7 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 5 Milliseconds
INFO - Service request (POST) /api2/user/messages took 47 Milliseconds
INFO - Service request (GET) /api2/pools/5/messages took 77 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (POST) /api2/user/messages took 35 Milliseconds
INFO - Service request (POST) /api2/user/messages took 35 Milliseconds
INFO - Service request (POST) /api2/user/messages took 100 Milliseconds
INFO - Service request (POST) /api2/user/messages took 28 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 26 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 7 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 4 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 3 Milliseconds
INFO - Service request (POST) /api2/user/messages took 28 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 9 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages took 26 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 2011 Milliseconds
Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.912 sec
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.057 sec
Running org.apache.esme.api.ApiSpecsAsTest
INFO - Service request (POST) /api/login took 24 Milliseconds
INFO - Service request (GET) /api/status took 4 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 4 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (POST) /api/login took 15 Milliseconds
INFO - Service request (GET) /api/logout took 2 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (POST) /api/login took 9 Milliseconds
INFO - Service request (GET) /api/status took 4 Milliseconds
INFO - Service request (GET) /api/logout took 6 Milliseconds
INFO - Service request (GET) /api/logout took 4 Milliseconds
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (GET) /api/logout took 4 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (GET) /api/status took 5 Milliseconds
INFO - Service request (POST) /api/send_msg took 7 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (POST) /api/send_msg took 4 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (POST) /api/add_action took 22 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_action took 17 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 11 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt took 7 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 3 Milliseconds
INFO - Service request (POST) /api/send_msg took 13 Milliseconds
Full(<esme_api success="true"><xml:group></xml:group></esme_api>)
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt87 took 6 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt8787 took 3 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (POST) /api/add_pool took 17 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/send_msg took 7 Milliseconds
Full(<esme_api msg="message parameter is missing" success="false"><xml:group></xml:group></esme_api>)
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.659 sec
Running org.apache.esme.api.TwitterAPISpecsAsTest
INFO - Service request (POST) /twitter/statuses/update.xml took 35 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 5 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 73 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 29 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 62 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 3 Milliseconds
INFO - Service request (POST) /twitter/friendships/create/twitter_user.xml took 44 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 19 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 5 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 14 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 7 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 7 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 23 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 7 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 39 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 52 Milliseconds
INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml took 74 Milliseconds
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.462 sec
Results :
Tests run: 118, Failures: 0, Errors: 0, Skipped: 0
[HUDSON] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[esme-server] in [<https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2]>
[INFO] Processing war project
[INFO] Copying webapp resources[<https://hudson.apache.org/hudson/job/ESME/ws/server/src/main/webapp]>
[INFO] Webapp assembled in[10655 msecs]
[INFO] Building war: <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war>
[INFO] [install:install {execution: default-install}]
[INFO] Installing <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war> to /export/home/hudson/.m2/repository/org/apache/esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war
[HUDSON] Archiving <https://hudson.apache.org/hudson/job/ESME/ws/server/pom.xml> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2011-01-17_12-21-55/archive/org.apache.esme/esme-server/apache-esme-1.2/pom.xml
[HUDSON] Archiving <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2011-01-17_12-21-55/archive/org.apache.esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war
Build timed out. Aborting
[WARNINGS] Skipping publisher since build result is FAILURE
Skipping Cobertura coverage report as build was not SUCCESS or better ...