See <https://hudson.apache.org/hudson/job/ESME/485/>
------------------------------------------ [...truncated 241 lines...] INFO - Service request (POST) /api2/session took 21 Milliseconds INFO - Service request (POST) /api2/session took 115 Milliseconds INFO - Service request (GET) /api2/users/4/tokens took 2 Milliseconds INFO - Service request (POST) /api2/session took 20 Milliseconds INFO - Service request (GET) /api2/users/4/tokens took 3 Milliseconds INFO - Service request (POST) /api2/session took 33 Milliseconds INFO - Service request (POST) /api2/users/6/tokens took 11 Milliseconds INFO - Service request (GET) /api2/users/6/tokens took 6 Milliseconds INFO - Service request (POST) /api2/session took 22 Milliseconds INFO - Service request (POST) /api2/session took 84 Milliseconds INFO - Service request (POST) /api2/users/4/tokens took 9 Milliseconds INFO - Service request (POST) /api2/session took 39 Milliseconds INFO - Service request (POST) /api2/users/4/tokens took 2 Milliseconds INFO - Service request (POST) /api2/session took 55 Milliseconds INFO - Service request (POST) /api2/user/messages took 88 Milliseconds INFO - Service request (GET) /api2/user/messages took 16 Milliseconds INFO - Service request (POST) /api2/session took 117 Milliseconds INFO - Service request (GET) /api2/user/messages took 3 Milliseconds INFO - Service request (POST) /api2/session took 28 Milliseconds INFO - Service request (GET) /api2/user/messages took 6 Milliseconds INFO - Service request (GET) /api2/user/messages took 2 Milliseconds INFO - Service request (POST) /api2/session took 21 Milliseconds INFO - Service request (GET) /api2/user/messages took 33 Milliseconds INFO - Service request (POST) /api2/session took 20 Milliseconds INFO - Service request (GET) /api2/user/messages took 2 Milliseconds INFO - Service request (POST) /api2/session took 22 Milliseconds INFO - Service request (POST) /api2/user/messages took 31 Milliseconds INFO - Service request (GET) /api2/user/messages took 7 Milliseconds INFO - Service request (POST) /api2/session took 65 Milliseconds INFO - Service request (GET) /api2/user/messages took 3 Milliseconds INFO - Service request (POST) /api2/session took 31 Milliseconds INFO - Service request (GET) /api2/user/messages took 3 Milliseconds INFO - Service request (GET) /api2/user/messages took 2011 Milliseconds INFO - Service request (POST) /api2/session took 24 Milliseconds INFO - Service request (POST) /api2/pools took 35 Milliseconds INFO - Service request (POST) /api2/user/messages took 96 Milliseconds INFO - Service request (GET) /api2/user/messages took 4 Milliseconds INFO - Service request (POST) /api2/session took 18 Milliseconds INFO - Service request (POST) /api2/user/messages took 2 Milliseconds INFO - Service request (POST) /api2/session took 19 Milliseconds INFO - Service request (POST) /api2/user/messages took 41 Milliseconds INFO - Service request (POST) /api2/session took 56 Milliseconds INFO - Service request (POST) /api2/user/messages took 69 Milliseconds INFO - Service request (POST) /api2/session took 186 Milliseconds INFO - Service request (GET) /api2/user/followees took 6 Milliseconds INFO - Service request (POST) /api2/session took 41 Milliseconds INFO - Service request (GET) /api2/user/followees took 3 Milliseconds INFO - Service request (POST) /api2/session took 82 Milliseconds INFO - Service request (POST) /api2/user/followees took 283 Milliseconds INFO - Service request (POST) /api2/session took 18 Milliseconds INFO - Service request (POST) /api2/user/followees took 2 Milliseconds INFO - Service request (POST) /api2/session took 17 Milliseconds INFO - Service request (GET) /api2/user/followers took 8 Milliseconds INFO - Service request (POST) /api2/session took 318 Milliseconds INFO - Service request (GET) /api2/user/followers took 2 Milliseconds INFO - Service request (POST) /api2/session took 19 Milliseconds INFO - Service request (GET) /api2/user/tracks took 19 Milliseconds INFO - Service request (POST) /api2/session took 19 Milliseconds INFO - Service request (GET) /api2/user/tracks took 2 Milliseconds INFO - Service request (POST) /api2/session took 41 Milliseconds INFO - Service request (POST) /api2/user/tracks took 11 Milliseconds INFO - Service request (POST) /api2/session took 19 Milliseconds INFO - Service request (POST) /api2/user/tracks took 2 Milliseconds INFO - Service request (POST) /api2/session took 48 Milliseconds INFO - Service request (POST) /api2/user/tracks took 3 Milliseconds INFO - Service request (DELETE) /api2/user/tracks/2 took 28 Milliseconds INFO - Service request (POST) /api2/session took 29 Milliseconds INFO - Service request (DELETE) /api2/user/tracks/1 took 2 Milliseconds INFO - Service request (POST) /api2/session took 45 Milliseconds INFO - Service request (GET) /api2/user/actions took 20 Milliseconds INFO - Service request (POST) /api2/session took 48 Milliseconds INFO - Service request (GET) /api2/user/actions took 3 Milliseconds INFO - Service request (POST) /api2/session took 66 Milliseconds INFO - Service request (POST) /api2/user/actions took 391 Milliseconds INFO - Service request (POST) /api2/session took 17 Milliseconds INFO - Service request (POST) /api2/user/actions took 2 Milliseconds INFO - Service request (POST) /api2/session took 17 Milliseconds INFO - Service request (POST) /api2/user/actions took 9 Milliseconds INFO - Service request (DELETE) /api2/user/actions/2 took 29 Milliseconds INFO - Service request (POST) /api2/session took 22 Milliseconds INFO - Service request (DELETE) /api2/user/actions/1 took 2 Milliseconds INFO - Service request (POST) /api2/session took 19 Milliseconds INFO - Service request (POST) /api2/user/messages took 21 Milliseconds INFO - Service request (POST) /api2/user/messages took 550 Milliseconds INFO - Service request (GET) /api2/conversations/9 took 17 Milliseconds INFO - Service request (POST) /api2/session took 40 Milliseconds INFO - Service request (GET) /api2/conversations/1 took 2 Milliseconds INFO - Service request (POST) /api2/session took 90 Milliseconds INFO - Service request (GET) /api2/conversations/10000 took 5 Milliseconds INFO - Service request (POST) /api2/session took 27 Milliseconds INFO - Service request (GET) /api2/pools took 23 Milliseconds INFO - Service request (POST) /api2/session took 33 Milliseconds INFO - Service request (GET) /api2/pools took 2 Milliseconds INFO - Service request (POST) /api2/session took 53 Milliseconds INFO - Service request (POST) /api2/pools took 6 Milliseconds INFO - Service request (POST) /api2/session took 80 Milliseconds INFO - Service request (POST) /api2/pools took 2 Milliseconds INFO - Service request (POST) /api2/session took 49 Milliseconds INFO - Service request (POST) /api2/pools took 6 Milliseconds INFO - Service request (POST) /api2/pools/3/users took 28 Milliseconds INFO - Service request (POST) /api2/session took 54 Milliseconds INFO - Service request (POST) /api2/pools/1/users took 2 Milliseconds INFO - Service request (POST) /api2/session took 20 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 23 Milliseconds INFO - Service request (GET) /api2/pools/4/messages took 7 Milliseconds INFO - Service request (POST) /api2/session took 16 Milliseconds INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds INFO - Service request (POST) /api2/session took 17 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 72 Milliseconds INFO - Service request (POST) /api2/pools took 5 Milliseconds INFO - Service request (POST) /api2/user/messages took 24 Milliseconds INFO - Service request (GET) /api2/pools/5/messages took 68 Milliseconds INFO - Service request (POST) /api2/session took 41 Milliseconds INFO - Service request (POST) /api2/pools took 5 Milliseconds INFO - Service request (POST) /api2/user/messages took 27 Milliseconds INFO - Service request (POST) /api2/user/messages took 73 Milliseconds INFO - Service request (POST) /api2/user/messages took 192 Milliseconds INFO - Service request (POST) /api2/user/messages took 21 Milliseconds INFO - Service request (GET) /api2/pools/6/messages took 25 Milliseconds INFO - Service request (GET) /api2/pools/6/messages took 7 Milliseconds INFO - Service request (POST) /api2/session took 25 Milliseconds INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds INFO - Service request (POST) /api2/session took 17 Milliseconds INFO - Service request (POST) /api2/pools took 4 Milliseconds INFO - Service request (GET) /api2/pools/6/messages took 2 Milliseconds INFO - Service request (POST) /api2/user/messages took 49 Milliseconds INFO - Service request (GET) /api2/pools/6/messages took 9 Milliseconds INFO - Service request (POST) /api2/session took 36 Milliseconds INFO - Service request (POST) /api2/session took 18 Milliseconds INFO - Service request (POST) /api2/pools took 4 Milliseconds INFO - Service request (GET) /api2/pools/7/messages took 2 Milliseconds INFO - Service request (POST) /api2/user/messages took 33 Milliseconds INFO - Service request (GET) /api2/pools/7/messages took 3 Milliseconds INFO - Service request (POST) /api2/session took 63 Milliseconds INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds INFO - Service request (POST) /api2/session took 16 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: 36.76 sec Running org.apache.esme.api.ApiSpecsAsTest INFO - Service request (POST) /api/login took 48 Milliseconds INFO - Service request (GET) /api/status took 3 Milliseconds INFO - Service request (GET) /api/status took 2 Milliseconds INFO - Service request (POST) /api/login took 7 Milliseconds INFO - Service request (POST) /api/login took 6 Milliseconds INFO - Service request (GET) /api/status took 4 Milliseconds INFO - Service request (POST) /api/login took 71 Milliseconds INFO - Service request (GET) /api/logout took 8 Milliseconds INFO - Service request (GET) /api/status took 3 Milliseconds INFO - Service request (POST) /api/login took 41 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 7 Milliseconds INFO - Service request (POST) /api/login took 50 Milliseconds INFO - Service request (GET) /api/logout took 6 Milliseconds INFO - Service request (GET) /api/logout took 5 Milliseconds INFO - Service request (POST) /api/login took 54 Milliseconds INFO - Service request (GET) /api/status took 3 Milliseconds INFO - Service request (POST) /api/send_msg took 9 Milliseconds INFO - Service request (POST) /api/send_msg took 4 Milliseconds INFO - Service request (POST) /api/login took 28 Milliseconds INFO - Service request (POST) /api/send_msg took 5 Milliseconds INFO - Service request (POST) /api/login took 30 Milliseconds INFO - Service request (POST) /api/add_action took 40 Milliseconds INFO - Service request (POST) /api/add_action took 7 Milliseconds INFO - Service request (POST) /api/add_action took 6 Milliseconds INFO - Service request (POST) /api/add_action took 6 Milliseconds INFO - Service request (POST) /api/add_action took 7 Milliseconds INFO - Service request (POST) /api/add_action took 8 Milliseconds INFO - Service request (POST) /api/add_action took 8 Milliseconds INFO - Service request (POST) /api/add_action took 8 Milliseconds INFO - Service request (POST) /api/add_action took 7 Milliseconds INFO - Service request (POST) /api/add_action took 9 Milliseconds INFO - Service request (POST) /api/add_action took 8 Milliseconds INFO - Service request (POST) /api/add_action took 15 Milliseconds INFO - Service request (POST) /api/add_action took 20 Milliseconds INFO - Service request (POST) /api/add_action took 13 Milliseconds INFO - Service request (POST) /api/add_action took 839 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 10 Milliseconds INFO - Service request (POST) /api/add_action took 14 Milliseconds INFO - Service request (POST) /api/add_action took 2 Milliseconds INFO - Service request (POST) /api/login took 28 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 4 Milliseconds INFO - Service request (POST) /api/add_action took 6 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 5 Milliseconds INFO - Service request (POST) /api/add_action took 5 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/send_msg took 8 Milliseconds Full(<esme_api success="true"><xml:group></xml:group></esme_api>) INFO - Service request (POST) /api/login took 60 Milliseconds INFO - Service request (POST) /api/add_pool/ttt87 took 16 Milliseconds INFO - Service request (POST) /api/add_pool/ttt8787 took 2 Milliseconds INFO - Service request (POST) /api/login took 32 Milliseconds INFO - Service request (POST) /api/add_pool took 31 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.754 sec Running org.apache.esme.lib.MsgParserSpecsAsTest Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.205 sec Running org.apache.esme.actor.PopStatsActorSpecsAsTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.052 sec Results : Tests run: 118, Failures: 0, Errors: 0, Skipped: 0 [HUDSON] Recording test results [INFO] [INFO] --- maven-war-plugin:2.1.1:war (default-war) @ esme-server --- [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 [16404 msecs] [INFO] Building war: <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2.war> [INFO] WEB-INF/web.xml already added, skipping [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ esme-server --- [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 [INFO] Installing <https://hudson.apache.org/hudson/job/ESME/ws/server/pom.xml> to /export/home/hudson/.m2/repository/org/apache/esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.pom projectSucceeded org.apache.esme:esme-server:apache-esme-1.2 [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-30_12-13-33/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-30_12-13-33/archive/org.apache.esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war sessionEnded [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 40:19.672s [INFO] Finished at: Sun Jan 30 12:56:55 GMT+00:00 2011 [INFO] Final Memory: 21M/165M [INFO] ------------------------------------------------------------------------ Sending e-mails to: [email protected] channel stopped [WARNINGS] Parsing warnings in console log... Publishing Cobertura coverage report... No coverage results were found using the pattern '**/target/site/cobertura/coverage.xml' relative to '<https://hudson.apache.org/hudson/job/ESME/ws/server'.> Did you enter a pattern relative to the correct directory? Did you generate the XML report(s) for Cobertura?
