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/20 13:37:42 UTC
Build failed in Hudson: ESME #476
See <https://hudson.apache.org/hudson/job/ESME/476/>
------------------------------------------
[...truncated 252 lines...]
INFO - Service request (GET) /api2/user/followees took 3 Milliseconds
INFO - Service request (POST) /api2/session took 10 Milliseconds
INFO - Service request (POST) /api2/user/followees took 65 Milliseconds
INFO - Service request (POST) /api2/session took 9 Milliseconds
INFO - Service request (POST) /api2/user/followees took 3 Milliseconds
INFO - Service request (POST) /api2/session took 10 Milliseconds
INFO - Service request (GET) /api2/user/followers took 12 Milliseconds
INFO - Service request (POST) /api2/session took 16 Milliseconds
INFO - Service request (GET) /api2/user/followers took 3 Milliseconds
INFO - Service request (POST) /api2/session took 10 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 116 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 15 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 2 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 47 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/1 took 3 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/actions took 31 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 6 Milliseconds
INFO - Service request (POST) /api2/user/actions took 140 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/actions took 3 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/user/actions took 41 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 took 54 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 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 32 Milliseconds
INFO - Service request (POST) /api2/user/messages took 263 Milliseconds
INFO - Service request (GET) /api2/conversations/9 took 25 Milliseconds
INFO - Service request (POST) /api2/session took 11 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 6 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (GET) /api2/pools took 30 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (GET) /api2/pools took 3 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 9 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 3 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 12 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/pools/1/users took 3 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/pools/3/users took 86 Milliseconds
INFO - Service request (POST) /api2/pools took 8 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 55 Milliseconds
INFO - Service request (POST) /api2/user/messages took 37 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 8 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 6 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 8 Milliseconds
INFO - Service request (POST) /api2/user/messages took 33 Milliseconds
INFO - Service request (GET) /api2/pools/5/messages took 109 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 55 Milliseconds
INFO - Service request (POST) /api2/user/messages took 61 Milliseconds
INFO - Service request (POST) /api2/user/messages took 103 Milliseconds
INFO - Service request (POST) /api2/user/messages took 44 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 40 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 10 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 4 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 4 Milliseconds
INFO - Service request (POST) /api2/user/messages took 54 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 12 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 8 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 3 Milliseconds
INFO - Service request (POST) /api2/user/messages took 238 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 3 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 4 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 2010 Milliseconds
Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 35.062 sec
Running org.apache.esme.api.ApiSpecsAsTest
INFO - Service request (POST) /api/login took 32 Milliseconds
INFO - Service request (GET) /api/status took 4 Milliseconds
INFO - Service request (GET) /api/status took 4 Milliseconds
INFO - Service request (POST) /api/login took 4 Milliseconds
INFO - Service request (POST) /api/login took 4 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 16 Milliseconds
INFO - Service request (GET) /api/logout took 3 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 3 Milliseconds
INFO - Service request (GET) /api/logout took 3 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 7 Milliseconds
INFO - Service request (GET) /api/status took 4 Milliseconds
INFO - Service request (POST) /api/send_msg took 12 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/send_msg took 3 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (POST) /api/add_action took 32 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 6 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 7 Milliseconds
INFO - Service request (POST) /api/add_action took 11 Milliseconds
INFO - Service request (POST) /api/add_action took 7 Milliseconds
INFO - Service request (POST) /api/add_action took 7 Milliseconds
INFO - Service request (POST) /api/add_action took 15 Milliseconds
INFO - Service request (POST) /api/add_action took 21 Milliseconds
INFO - Service request (POST) /api/add_action took 12 Milliseconds
INFO - Service request (POST) /api/add_action took 25 Milliseconds
INFO - Service request (POST) /api/add_action took 27 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt took 11 Milliseconds
INFO - Service request (POST) /api/add_action took 28 Milliseconds
INFO - Service request (POST) /api/add_action took 13 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/login took 6 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 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 5 Milliseconds
INFO - Service request (POST) /api/add_action took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 7 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/send_msg took 7 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 7 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt8787 took 4 Milliseconds
INFO - Service request (POST) /api/login took 8 Milliseconds
INFO - Service request (POST) /api/add_pool took 33 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/send_msg took 4 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.403 sec
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.271 sec
Running org.apache.esme.api.TwitterAPISpecsAsTest
INFO - Service request (POST) /twitter/statuses/update.xml took 368 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 4 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 136 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 75 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 57 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 72 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 23 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 7 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 19 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 10 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 7 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 27 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 7 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 38 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 162 Milliseconds
INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml took 244 Milliseconds
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.837 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[14384 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-20_12-31-37/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-20_12-31-37/archive/org.apache.esme/esme-server/apache-esme-1.2/esme-server-apache-esme-1.2.war
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5 minutes 51 seconds
[INFO] Finished at: Thu Jan 20 07:37:39 EST 2011
[INFO] Final Memory: 40M/319M
[INFO] ------------------------------------------------------------------------
Waiting for Hudson to finish collecting data
ERROR: Processing failed due to a bug in the code. Please report this to users@hudson.dev.java.net
<https://hudson.apache.org/hudson/job/ESME/ws/server> does not exist.
at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:474)
at hudson.plugins.violations.ViolationsCollector.findFiles(ViolationsCollector.java:215)
at hudson.plugins.violations.ViolationsCollector.doType(ViolationsCollector.java:166)
at hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:110)
at hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:27)
at hudson.FilePath.act(FilePath.java:753)
at hudson.FilePath.act(FilePath.java:735)
at hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end(ViolationsMavenReporter.java:96)
at hudson.maven.MavenModuleSetBuild$Builder.end(MavenModuleSetBuild.java:740)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:539)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
at hudson.model.Run.run(Run.java:1324)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:349)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:139)
project=hudson.maven.MavenModuleSet@3de53889[ESME]
project.getModules()=[hudson.maven.MavenModule@68efb2ab[ESME/org.apache.esme:esme-server]]
project.getRootModule()=hudson.maven.MavenModule@68efb2ab[ESME/org.apache.esme:esme-server]
FATAL: <https://hudson.apache.org/hudson/job/ESME/ws/server> does not exist.
<https://hudson.apache.org/hudson/job/ESME/ws/server> does not exist.
at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:474)
at hudson.plugins.violations.ViolationsCollector.findFiles(ViolationsCollector.java:215)
at hudson.plugins.violations.ViolationsCollector.doType(ViolationsCollector.java:166)
at hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:110)
at hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:27)
at hudson.FilePath.act(FilePath.java:753)
at hudson.FilePath.act(FilePath.java:735)
at hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end(ViolationsMavenReporter.java:96)
at hudson.maven.MavenModuleSetBuild$Builder.end(MavenModuleSetBuild.java:740)
at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:539)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
at hudson.model.Run.run(Run.java:1324)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:349)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:139)