www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject [Hudson] Cactus build 378 stuck - killed
Date Fri, 05 Feb 2010 08:13:34 GMT
Hi,

I killed the running Cactus job, which had been running for 8 hours. 
Looking at past builds it should have finished in less than 20 minutes.
I'm wondering if Hudson is in some kind of trouble, as there are many 
jobs that have been running for 3 - 8 hours. Further, there is no 
console output for a job I scheduled that has been running for several 
hours now.

FYI, here's the last output from the Cactus build (console output):
-------------------------------------------------------

  T E S T S
-------------------------------------------------------
Running org.apache.cactus.internal.util.TestStringUtil
log4j:WARN No appenders could be found for logger (org.apache.cactus.internal.util.StringUtil).
log4j:WARN Please initialize the log4j system properly.
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running org.apache.cactus.internal.client.TestWebTestResultParser
...
Running org.apache.cactus.internal.server.runner.TestXMLFormatter
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec

Results :

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

Killing the job resulted in the following output (is this normal when killing a job?):
[HUDSON] Recording test resultsERROR: Failed to parse POMs
hudson.remoting.ChannelClosedException: channel is already closed
	at hudson.remoting.Channel.send(Channel.java:408)
	at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:112)
	at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:100)
	at hudson.remoting.RemoteOutputStream.write(RemoteOutputStream.java:110)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
	at java.io.BufferedOutputStream.write(BufferedOutputStream.java:109)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
	at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1784)
	at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:691)
	at hudson.remoting.Channel.send(Channel.java:414)
	at hudson.remoting.Request.call(Request.java:149)
	at hudson.remoting.Channel.call(Channel.java:547)
	at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:156)
	at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:480)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
	at hudson.model.Run.run(Run.java:1179)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:122)
FATAL: channel is already closed
hudson.remoting.ChannelClosedException: channel is already closed
	at hudson.remoting.Channel.send(Channel.java:408)
	at hudson.remoting.Request.call(Request.java:105)
	at hudson.remoting.Channel.call(Channel.java:547)
	at hudson.Launcher$RemoteLauncher.kill(Launcher.java:734)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:422)
	at hudson.model.Run.run(Run.java:1179)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:304)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:122)


Last, CXF-Trunk-JDK16 #267 took the slot that Cactus used, let's see if that job is able to
finish (estimated to ~ 1 hour).


Regards,
-- 
Kristian


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message