The build seems to be timing out a lot lately. Do we know if anything has changed with Hudson? No major changes with ESME come to mind.
Ethan On Mon, Jan 3, 2011 at 1:42 PM, Apache Hudson Server <[email protected]> wrote: > See <https://hudson.apache.org/hudson/job/ESME/459/> > > ------------------------------------------ > [...truncated 340 lines...] > INFO - Service request (POST) /api2/user/tracks took 2 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 6 Milliseconds > INFO - Service request (DELETE) /api2/user/tracks/1 took 2 Milliseconds > INFO - Service request (GET) /api2/user/actions took 15 Milliseconds > INFO - Service request (POST) /api2/session took 7 Milliseconds > INFO - Service request (GET) /api2/user/actions took 2 Milliseconds > INFO - Service request (POST) /api2/user/actions took 66 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/user/actions took 27 Milliseconds > INFO - Service request (DELETE) /api2/user/actions/2 took 25 Milliseconds > INFO - Service request (POST) /api2/session took 6 Milliseconds > INFO - Service request (DELETE) /api2/user/actions/1 took 1 Milliseconds > INFO - Service request (POST) /api2/user/messages took 62 Milliseconds > :6:7: expected closing tag of hr > ^ > INFO - Service request (POST) /api2/user/messages took 130 Milliseconds > INFO - Service request (GET) /api2/conversations/9 took 25 Milliseconds > INFO - Service request (POST) /api2/session took 6 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 7 Milliseconds > INFO - Service request (GET) /api2/pools took 20 Milliseconds > INFO - Service request (POST) /api2/session took 6 Milliseconds > INFO - Service request (GET) /api2/pools took 2 Milliseconds > INFO - Service request (POST) /api2/pools took 15 Milliseconds > INFO - Service request (POST) /api2/session took 6 Milliseconds > INFO - Service request (POST) /api2/pools took 2 Milliseconds > INFO - Service request (POST) /api2/pools took 8 Milliseconds > INFO - Service request (POST) /api2/pools/3/users took 29 Milliseconds > INFO - Service request (POST) /api2/session took 5 Milliseconds > INFO - Service request (POST) /api2/pools/1/users took 1 Milliseconds > INFO - Service request (POST) /api2/pools took 8 Milliseconds > INFO - Service request (GET) /api2/pools/4/messages took 10 Milliseconds > INFO - Service request (POST) /api2/user/messages took 35 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 5 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 3 Milliseconds > INFO - Service request (POST) /api2/pools took 7 Milliseconds > INFO - Service request (POST) /api2/user/messages took 35 Milliseconds > INFO - Service request (GET) /api2/pools/5/messages took 83 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 40 Milliseconds > INFO - Service request (POST) /api2/user/messages took 46 Milliseconds > INFO - Service request (POST) /api2/user/messages took 48 Milliseconds > INFO - Service request (POST) /api2/user/messages took 314 Milliseconds > INFO - Service request (GET) /api2/pools/6/messages took 29 Milliseconds > INFO - Service request (GET) /api2/pools/6/messages took 8 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/pools took 4 Milliseconds > INFO - Service request (GET) /api2/pools/6/messages took 2 Milliseconds > INFO - Service request (POST) /api2/user/messages took 34 Milliseconds > INFO - Service request (GET) /api2/pools/6/messages took 9 Milliseconds > INFO - Service request (POST) /api2/session 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/7/messages took 2 Milliseconds > INFO - Service request (POST) /api2/user/messages took 63 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 3 Milliseconds > INFO - Service request (GET) /api2/pools/1/messages took 2 Milliseconds > INFO - Service request (GET) /api2/pools/1/messages took 2011 Milliseconds > Tests run: 66, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 32.395 sec > Running org.apache.esme.actor.PopStatsActorSpecsAsTest > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.056 sec > Running org.apache.esme.api.ApiSpecsAsTest > INFO - Service request (POST) /api/login took 15 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 6 Milliseconds > INFO - Service request (GET) /api/logout took 3 Milliseconds > INFO - Service request (GET) /api/status took 3 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 3 Milliseconds > INFO - Service request (POST) /api/login took 34 Milliseconds > INFO - Service request (GET) /api/logout took 2 Milliseconds > INFO - Service request (GET) /api/logout took 1 Milliseconds > INFO - Service request (POST) /api/login took 6 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 1 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 11 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 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 18 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 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 9 Milliseconds > :6:7: expected closing tag of hr > ^ > INFO - Service request (POST) /api/add_action took 2 Milliseconds > INFO - Service request (POST) /api/login took 10 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 2 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 3 Milliseconds > INFO - Service request (POST) /api/add_action took 7 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 6 Milliseconds > Full(<esme_api success="true"><xml:group></xml:group></esme_api>) > INFO - Service request (POST) /api/login took 8 Milliseconds > INFO - Service request (POST) /api/add_pool/ttt87 took 9 Milliseconds > INFO - Service request (POST) /api/add_pool/ttt8787 took 9 Milliseconds > INFO - Service request (POST) /api/login took 5 Milliseconds > INFO - Service request (POST) /api/add_pool took 164 Milliseconds > INFO - Service request (POST) /api/send_msg took 6 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.907 sec > Running org.apache.esme.api.TwitterAPISpecsAsTest > INFO - Service request (POST) /twitter/statuses/update.xml took 124 > Milliseconds > INFO - Service request (POST) /twitter/statuses/update.xml took 3 Milliseconds > INFO - Service request (POST) /twitter/statuses/update.xml took 2 Milliseconds > INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 91 > Milliseconds > INFO - Service request (GET) /twitter/statuses/user_timeline.xml took 21 > Milliseconds > INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 37 > 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 27 Milliseconds > INFO - Service request (GET) /twitter/statuses/followers.xml took 8 > Milliseconds > INFO - Service request (GET) /twitter/statuses/followers.xml took 3 > Milliseconds > INFO - Service request (GET) /twitter/statuses/friends.xml took 5 Milliseconds > INFO - Service request (GET) /twitter/statuses/friends.xml took 12 > Milliseconds > INFO - Service request (POST) /twitter/statuses/update.xml took 6 Milliseconds > INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 21 > Milliseconds > INFO - Service request (POST) /twitter/statuses/update.xml took 5 Milliseconds > INFO - Service request (GET) /twitter/statuses/home_timeline.xml took 29 > Milliseconds > INFO - Service request (GET) /twitter/statuses/public_timeline.xml took 78 > Milliseconds > INFO - Service request (POST) /twitter/friendships/destroy/twitter_user.xml > took 55 Milliseconds > Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.455 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-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[8716 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 > [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-03_12-12-48/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/2011-01-03_12-12-48/archive/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:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > 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: 28 minutes 39 seconds > [INFO] Finished at: Mon Jan 03 12:44:10 GMT+00:00 2011 > [INFO] Final Memory: 39M/371M > [INFO] > ------------------------------------------------------------------------ > [WARNINGS] Skipping publisher since build result is FAILURE > >
