esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Hudson Server <hud...@hudson.apache.org>
Subject Build failed in Hudson: ESME #471
Date Sat, 15 Jan 2011 12:21:03 GMT
See <https://hudson.apache.org/hudson/job/ESME/471/>

------------------------------------------
[...truncated 263 lines...]
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 35 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/followees took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/followers took 7 Milliseconds
INFO - Service request (POST) /api2/session took 5 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 17 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 2 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 5 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 5 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 18 Milliseconds
INFO - Service request (POST) /api2/session took 5 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 47 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/actions took 3 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/actions took 27 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 took 29 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/messages took 23 Milliseconds
INFO - Service request (POST) /api2/user/messages took 65 Milliseconds
INFO - Service request (GET) /api2/conversations/9 took 19 Milliseconds
INFO - Service request (POST) /api2/session took 10 Milliseconds
INFO - Service request (GET) /api2/conversations/1 took 3 Milliseconds
INFO - Service request (POST) /api2/session took 9 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 took 5 Milliseconds
INFO - Service request (POST) /api2/session took 8 Milliseconds
INFO - Service request (GET) /api2/pools took 25 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/pools took 2 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 19 Milliseconds
INFO - Service request (POST) /api2/session took 5 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 7 Milliseconds
INFO - Service request (POST) /api2/pools/3/users took 32 Milliseconds
INFO - Service request (POST) /api2/session took 6 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 8 Milliseconds
INFO - Service request (POST) /api2/user/messages took 31 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 4 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 3 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/pools took 5 Milliseconds
INFO - Service request (POST) /api2/user/messages took 51 Milliseconds
INFO - Service request (GET) /api2/pools/5/messages took 59 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 29 Milliseconds
INFO - Service request (POST) /api2/user/messages took 30 Milliseconds
INFO - Service request (POST) /api2/user/messages took 27 Milliseconds
INFO - Service request (POST) /api2/user/messages took 25 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 27 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 21 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 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 (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 5 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 1 Milliseconds
INFO - Service request (POST) /api2/user/messages took 24 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 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 (GET) /api2/pools/1/messages took 2003 Milliseconds
Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 30.906 sec
Running org.apache.esme.api.ApiSpecsAsTest
INFO - Service request (POST) /api/login took 20 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 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 10 Milliseconds
INFO - Service request (GET) /api/logout took 2 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (GET) /api/logout took 2 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (GET) /api/logout took 3 Milliseconds
INFO - Service request (GET) /api/logout took 2 Milliseconds
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (POST) /api/send_msg took 5 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 2 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (POST) /api/add_action took 18 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 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 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 20 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 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 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 4 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 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 4 Milliseconds
Full(<esme_api success="true"><xml:group></xml:group></esme_api>)
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt87 took 9 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt8787 took 2 Milliseconds
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (POST) /api/add_pool took 14 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: 6.08 sec
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.02 sec
Running org.apache.esme.api.TwitterAPISpecsAsTest
INFO - Service request (POST) /twitter/statuses/update.xml took 34 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 4 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 2 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 34 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 2 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 2 Milliseconds
INFO - Service request (POST) /twitter/friendships/create/twitter_user.xml took 41 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 17 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 3 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 13 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 8 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 6 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 22 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 6 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 36 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 50 Milliseconds
INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml took 45 Milliseconds
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.231 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[1133 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 /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-15_12-15-09/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-15_12-15-09/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 42 seconds
[INFO] Finished at: Sat Jan 15 04:21:02 PST 2011
[INFO] Final Memory: 36M/152M
[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@5c9d2ef2[ESME]
project.getModules()=[hudson.maven.MavenModule@2c95be12[ESME/org.apache.esme:esme-server]]
project.getRootModule()=hudson.maven.MavenModule@2c95be12[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)


Mime
View raw message