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.zones.apache.org> on 2010/07/22 15:39:26 UTC
Build failed in Hudson: ESME #294
See <http://hudson.zones.apache.org/hudson/job/ESME/294/>
------------------------------------------
[...truncated 459 lines...]
INFO - Service request (POST) /api2/users/4/tokens took 6 Milliseconds
INFO - Service request (GET) /api2/users/4/tokens took 4 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens took 2 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/users/2/tokens took 1 Milliseconds
INFO - Service request (POST) /api2/user/messages took 130 Milliseconds
INFO - Service request (GET) /api2/user/messages took 5 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/messages took 1 Milliseconds
INFO - Service request (POST) /api2/session took 30 Milliseconds
INFO - Service request (GET) /api2/user/messages took 5 Milliseconds
INFO - Service request (GET) /api2/user/messages took 2 Milliseconds
INFO - Service request (GET) /api2/user/messages took 35 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (GET) /api2/user/messages took 1 Milliseconds
INFO - Service request (POST) /api2/user/messages took 162 Milliseconds
INFO - Service request (GET) /api2/user/messages took 4 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/messages took 1 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (GET) /api2/user/messages took 2 Milliseconds
INFO - Service request (GET) /api2/user/messages took 2002 Milliseconds
INFO - Service request (POST) /api2/pools took 42 Milliseconds
INFO - Service request (POST) /api2/user/messages took 178 Milliseconds
INFO - Service request (GET) /api2/user/messages took 20 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/messages took 1 Milliseconds
INFO - Service request (GET) /api2/user/followees took 16 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (GET) /api2/user/followees took 1 Milliseconds
INFO - Service request (POST) /api2/user/followees took 158 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/user/followees took 2 Milliseconds
INFO - Service request (GET) /api2/user/followers took 6 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (GET) /api2/user/followers took 1 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 10 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (GET) /api2/user/tracks took 1 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 11 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 1 Milliseconds
INFO - Service request (POST) /api2/user/tracks took 5 Milliseconds
INFO - Service request (DELETE) /api2/user/tracks/2 took 24 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 12 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (GET) /api2/user/actions took 1 Milliseconds
INFO - Service request (POST) /api2/user/actions took 48 Milliseconds
INFO - Service request (POST) /api2/session took 13 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 21 Milliseconds
INFO - Service request (POST) /api2/session took 7 Milliseconds
INFO - Service request (DELETE) /api2/user/actions/1 took 1 Milliseconds
INFO - Service request (POST) /api2/user/messages took 150 Milliseconds
INFO - Service request (POST) /api2/user/messages took 214 Milliseconds
INFO - Service request (GET) /api2/conversations/9 took 29 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 5 Milliseconds
INFO - Service request (GET) /api2/conversations/10000 took 13 Milliseconds
INFO - Service request (GET) /api2/pools took 18 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 7 Milliseconds
INFO - Service request (POST) /api2/session took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 1 Milliseconds
INFO - Service request (POST) /api2/pools took 9 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 4 Milliseconds
INFO - Service request (POST) /api2/pools took 8 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 8 Milliseconds
INFO - Service request (POST) /api2/user/messages took 190 Milliseconds
INFO - Service request (GET) /api2/pools/4/messages took 12 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 (GET) /api2/pools/1/messages took 5 Milliseconds
INFO - Service request (GET) /api2/pools/1/messages took 6 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 115 Milliseconds
INFO - Service request (GET) /api2/pools/5/messages took 68 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/pools took 7 Milliseconds
INFO - Service request (POST) /api2/user/messages took 112 Milliseconds
INFO - Service request (POST) /api2/user/messages took 115 Milliseconds
INFO - Service request (POST) /api2/user/messages took 108 Milliseconds
INFO - Service request (POST) /api2/user/messages took 104 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 28 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 24 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 3 Milliseconds
INFO - Service request (POST) /api2/user/messages took 105 Milliseconds
INFO - Service request (GET) /api2/pools/6/messages took 10 Milliseconds
INFO - Service request (POST) /api2/session took 4 Milliseconds
INFO - Service request (POST) /api2/session took 5 Milliseconds
INFO - Service request (POST) /api2/pools took 6 Milliseconds
INFO - Service request (GET) /api2/pools/7/messages took 2 Milliseconds
INFO - Service request (POST) /api2/user/messages took 96 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 2002 Milliseconds
Tests run: 64, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.13 sec
Running org.apache.esme.actor.PopStatsActorSpecsAsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.014 sec
Running org.apache.esme.api.ApiSpecsAsTest
INFO - Service request (POST) /api/login took 12 Milliseconds
INFO - Service request (GET) /api/status took 3 Milliseconds
INFO - Service request (GET) /api/status took 1 Milliseconds
INFO - Service request (POST) /api/login took 2 Milliseconds
INFO - Service request (POST) /api/login took 2 Milliseconds
INFO - Service request (GET) /api/status took 1 Milliseconds
INFO - Service request (POST) /api/login took 5 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 4 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 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 5 Milliseconds
INFO - Service request (POST) /api/send_msg took 2 Milliseconds
INFO - Service request (POST) /api/login took 4 Milliseconds
INFO - Service request (POST) /api/add_action took 11 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/add_action took 7 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 5 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 5 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_action took 26 Milliseconds
INFO - Service request (POST) /api/add_action took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 18 Milliseconds
INFO - Service request (POST) /api/add_action took 10 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt took 9 Milliseconds
INFO - Service request (POST) /api/add_action took 12 Milliseconds
INFO - Service request (POST) /api/add_action took 31 Milliseconds
INFO - Service request (POST) /api/add_action took 2 Milliseconds
INFO - Service request (POST) /api/login took 5 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 2 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 3 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 3 Milliseconds
INFO - Service request (POST) /api/add_action took 4 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 4 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt87 took 5 Milliseconds
INFO - Service request (POST) /api/add_pool/ttt8787 took 1 Milliseconds
INFO - Service request (POST) /api/login took 6 Milliseconds
INFO - Service request (POST) /api/add_pool took 17 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: 8.059 sec
Results :
Tests run: 102, 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 [<http://hudson.zones.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.0-RC1-incubating]>
[INFO] Processing war project
[INFO] Copying webapp resources[<http://hudson.zones.apache.org/hudson/job/ESME/ws/server/src/main/webapp]>
[INFO] Webapp assembled in[1249 msecs]
[INFO] Building war: <http://hudson.zones.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.0-RC1-incubating.war>
[INFO] [install:install {execution: default-install}]
[INFO] Installing <http://hudson.zones.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.0-RC1-incubating.war> to /home/hudson/.m2/repository/org/apache/esme/esme-server/apache-esme-1.0-RC1-incubating/esme-server-apache-esme-1.0-RC1-incubating.war
[HUDSON] Archiving <http://hudson.zones.apache.org/hudson/job/ESME/ws/server/pom.xml> to /export/home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2010-07-22_13-30-35/archive/org.apache.esme/esme-server/apache-esme-1.0-RC1-incubating/pom.xml
[HUDSON] Archiving <http://hudson.zones.apache.org/hudson/job/ESME/ws/server/target/esme-server-apache-esme-1.0-RC1-incubating.war> to /export/home/hudson/hudson/jobs/ESME/modules/org.apache.esme$esme-server/builds/2010-07-22_13-30-35/archive/org.apache.esme/esme-server/apache-esme-1.0-RC1-incubating/esme-server-apache-esme-1.0-RC1-incubating.war
Build timed out. Aborting
channel stopped
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
channel is already closed
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.reflect.UndeclaredThrowableException
at $Proxy2.isArchivingDisabled(Unknown Source)
at hudson.maven.MavenBuildProxy$Filter.isArchivingDisabled(MavenBuildProxy.java:210)
at hudson.maven.reporters.MavenArtifact.archive(MavenArtifact.java:192)
at hudson.maven.reporters.MavenArtifactArchiver.postBuild(MavenArtifactArchiver.java:109)
at hudson.maven.MavenModuleSetBuild$Builder.postModule(MavenModuleSetBuild.java:729)
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:696)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:640)
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:619)
Caused by: hudson.remoting.ChannelClosedException: channel is already closed
at hudson.remoting.Channel.send(Channel.java:412)
at hudson.remoting.Request.call(Request.java:105)
at hudson.remoting.Channel.call(Channel.java:551)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158)
... 30 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 minutes 8 seconds
[INFO] Finished at: Thu Jul 22 13:40:28 UTC 2010
[WARNINGS] Skipping publisher since build result is FAILURE
Hudson build is back to normal : ESME #296
Posted by Apache Hudson Server <hu...@hudson.zones.apache.org>.
See <http://hudson.zones.apache.org/hudson/job/ESME/296/changes>
Build failed in Hudson: ESME #295
Posted by Apache Hudson Server <hu...@hudson.zones.apache.org>.
See <http://hudson.zones.apache.org/hudson/job/ESME/295/>
------------------------------------------
Started by timer
Building remotely on minerva.apache.org (Ubuntu)
Updating http://svn.apache.org/repos/asf/incubator/esme/trunk/server
At revision 967061
no change for http://svn.apache.org/repos/asf/incubator/esme/trunk/server since the previous build
Parsing POMs
Build timed out. Aborting
[WARNINGS] Skipping publisher since build result is FAILURE