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 2010/11/10 14:50:25 UTC

Build failed in Hudson: ESME #404

See <https://hudson.apache.org/hudson/job/ESME/404/changes>

Changes:

[esjewett] [ESME-306] Adds update box to search display.

[esjewett] [ESME-305] Fixes search in local build - I had broken it when refactoring the message_core.html template.

------------------------------------------
[...truncated 337 lines...]
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 1 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 1 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 4 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/2 took 25 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/1 took 1 Milliseconds
INFO - Service request (GET) /api2/user/actions took 13 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (GET) /api2/user/actions took 2 Milliseconds
INFO - Service request (POST) /api2/user/actions took 56 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/actions took 2 Milliseconds
INFO - Service request (POST) /api2/user/actions took 12 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/2 took 142 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages took 41 Milliseconds
INFO - Service request (POST) /api2/user/messages took 74 Milliseconds
INFO - Service request (GET) /api2/conversations/9 took 23 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/conversations/1 took 1 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 took 6 Milliseconds
INFO - Service request (GET) /api2/pools took 17 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (GET) /api2/pools took 1 Milliseconds
INFO - Service request (POST) /api2/pools took 12 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/pools took 2 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/pools/3/users took 26 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/pools/1/users took 2 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 68 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 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 2 Milliseconds
INFO - Service request (POST) /api2/pools took 5 Milliseconds
INFO - Service request (POST) /api2/user/messages took 241 Milliseconds
INFO - Service request (GET) /api2/pools/5/messages took 63 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 31 Milliseconds
INFO - Service request (POST) /api2/user/messages took 30 Milliseconds
INFO - Service request (POST) /api2/user/messages took 74 Milliseconds
INFO - Service request (POST) /api2/user/messages took 41 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 28 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/pools took 4 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages took 30 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 4 Milliseconds
INFO - Service request (POST) /api2/pools took 5 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages took 27 Milliseconds
INFO - Service request (GET) /api2/pools/7/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 (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: 31.937 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 13 Milliseconds
INFO - Service request (GET) /api/status took 4 Milliseconds
INFO - Service request (GET) /api/status took 1 Milliseconds
INFO - Service request (POST) /api/login took 3 Milliseconds
INFO - Service request (POST) /api/login 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/logout took 2 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (POST) /api/login took 7 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 3 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (GET) /api/logout took 2 Milliseconds
INFO - Service request (GET) /api/logout took 2 Milliseconds
INFO - Service request (POST) /api/login took 7 Milliseconds
INFO - Service request (GET) /api/status took 2 Milliseconds
INFO - Service request (POST) /api/send_msg took 8 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 2 Milliseconds
INFO - Service request (POST) /api/login took 5 Milliseconds
INFO - Service request (POST) /api/add_action took 12 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 10 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 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 6 Milliseconds
INFO - Service request (POST) /api/add_action took 12 Milliseconds
INFO - Service request (POST) /api/add_action took 19 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 11 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 11 Milliseconds
INFO - Service request (POST) /api/add_action took 8 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 2 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 3 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 4 Milliseconds
INFO - Service request (POST) /api/add_action took 4 Milliseconds
INFO - Service request (POST) /api/send_msg took 6 Milliseconds
Full(<esme_api success="true"><xml:group></xml:group></esme_api>)
INFO - Service request (POST) /api/login took 7 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt87 took 5 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt8787 took 2 Milliseconds
INFO - Service request (POST) /api/login took 4 Milliseconds
INFO - Service request (POST) /api/add_pool took 19 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.008 sec
Running org.apache.esme.api.TwitterAPISpecsAsTest
INFO - Service request (POST) /twitter/statuses/update.xml took 27 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 4 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 1 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 67 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 20 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 32 Milliseconds
INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 2 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 1 Milliseconds
INFO - Service request (POST) /twitter/friendships/create/twitter_user.xml took 29 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 10 Milliseconds
INFO - Service request (GET) /twitter/statuses/followers.xml took 4 Milliseconds
INFO - Service request (GET) /twitter/statuses/friends.xml took 5 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 22 Milliseconds
INFO - Service request (POST) /twitter/statuses/update.xml took 6 Milliseconds
INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 38 Milliseconds
INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 77 Milliseconds
INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml took 38 Milliseconds
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.761 sec

Results :

Tests run: 118, Failures: 0, Errors: 0, Skipped: 0

[HUDSON] Recording test results
[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/2010-11-10_12-39-29/archive/org.apache.esme/esme-server/apache-esme-1.2-incubating/pom.xml
[HUDSON] Archiving <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2-incubating.war> to /home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2010-11-10_12-39-29/archive/org.apache.esme/esme-server/apache-esme-1.2-incubating/esme-server-apache-esme-1.2-incubating.war
[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-incubating]>
[INFO] Processing war project
[INFO] Copying webapp resources[<https://hudson.apache.org/hudson/job/ESME/ws/server/src/main/webapp]>
[INFO] Webapp assembled in[31040 msecs]
[INFO] Building war: <https://hudson.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.2-incubating.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-incubating.war> to /export/home/hudson/.m2/repository/org/apache/esme/esme-server/apache-esme-1.2-incubating/esme-server-apache-esme-1.2-incubating.war
Build timed out. Aborting
channel stopped
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.reflect.UndeclaredThrowableException
	at $Proxy2.isArchivingDisabled(Unknown Source)
	at hudson.maven.MavenBuildProxy$Filter.isArchivingDisabled(MavenBuildProxy.java:222)
	at hudson.maven.reporters.MavenArtifact.archive(MavenArtifact.java:192)
	at hudson.maven.reporters.MavenArtifactArchiver.postBuild(MavenArtifactArchiver.java:107)
	at hudson.maven.MavenModuleSetBuild$Builder.postModule(MavenModuleSetBuild.java:800)
	at hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:317)
	at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:275)
	at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:68)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at hudson.maven.agent.Main.launch(Main.java:165)
	at hudson.maven.MavenBuilder.call(MavenBuilder.java:165)
	at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:750)
	at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:694)
	at hudson.remoting.UserRequest.perform(UserRequest.java:114)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:270)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
	at java.lang.Thread.run(Thread.java:619)
Caused by: hudson.remoting.ChannelClosedException: channel is already closed
	at hudson.remoting.Channel.send(Channel.java:467)
	at hudson.remoting.Request.call(Request.java:105)
	at hudson.remoting.Channel.call(Channel.java:630)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158)
	... 30 more
Caused by: hudson.remoting.Channel$OrderlyShutdown
	at hudson.remoting.Channel$CloseCommand.execute(Channel.java:764)
	at hudson.remoting.Channel$ReaderThread.run(Channel.java:963)
Caused by: Command close created at
	at hudson.remoting.Command.<init>(Command.java:58)
	at hudson.remoting.Command.<init>(Command.java:47)
	at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:760)
	at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:760)
	at hudson.remoting.Channel.close(Channel.java:805)
	at hudson.slaves.Channels$1.close(Channels.java:91)
	at hudson.maven.ProcessCache$MavenProcess.discard(ProcessCache.java:145)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:541)
	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)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 64 minutes 26 seconds
[INFO] Finished at: Wed Nov 10 13:51:28 GMT+00:00 2010
[INFO] Final Memory: 36M/215M
[INFO] ------------------------------------------------------------------------
[WARNINGS] Skipping publisher since build result is FAILURE

Hudson build is back to normal : ESME #405

Posted by Apache Hudson Server <hu...@hudson.apache.org>.

See <https://hudson.apache.org/hudson/job/ESME/405/>