Community
Participate
Working Groups
Since yesterday Hudson seems to react way slower than usual. My builds get *stuck* with this message in the log: Process leaked file descriptors. See http://wiki.hudson-ci.org/display/HUDSON/Spawning+processes+from+build for more information (link leads to nowhere) Other builds look stuck, too. I tried to change my job from slave1 to master and while I was still editing the job config all of a sudden the page behaved as if I had pressed "Submit". But I didn't! My config changes have been *partly* saved.
On master it now gets stuck already in the initial SVN checkout phase: https://hudson.eclipse.org/hudson/job/emf-cdo-integration/1650/console
*** Bug 351687 has been marked as a duplicate of this bug. ***
The linked text basically says that if a child process spawns another task which fails to correctly close all of it's inherited file descriptors it can cause this. Just to be on the safe side I restarted hudson this morning. -M.
The Virgo builds are still going haywire, so I guess there are still major problems with slave1.
Our Hudson instance is relatively old and has many known quirks. Should we plan on an upgrade soon-ish before too much action starts happening?
Please plan an upgrade soon. I would very much like a more resent Buckminster plugin for Hudson. If I've understood it correctly, it's not possible to update using the current Hudson.
I've been going through the recent change log and while I'd like to move us to 2.0.1 the fact is there seem to be bugs around CVS polling which are fixed in 2.1.0. So even though it's not quite a month old I'm going to try deploying 2.1.0 to the sandbox and I'll leave it run for a few days. If everything seems happy I'll look at updating the master instance. -M.
(In reply to comment #5) > Our Hudson instance is relatively old and has many known quirks. Should we > plan on an upgrade soon-ish before too much action starts happening? We are down to the final few weeks of Indigo SR1. It will be released 9/23. But, then Juno M2 is due on 9/30. So ... one approach would be to wait until 9/30 to tinker with build machine ... or, if you feel confident, in either Hudson or the ability to back out, then I'd suggest a change quickly, such as within a week (to avoid a very last minute change). HTH
Based on David's comments I've decided to hold of on the update until the first week in October. -M.
One concern I have with the latest Hudson 2.1.1 release are these bugs which break the Gerrit Trigger plug-in (not sure if EGit is using that) and causes errors in the XML REST interface for jobs hosted in Git: HUDSON-9008: java.lang.NoClassDefFoundError: org/spearce/jgit/lib/ObjectId when setting git choosing strategy http://issues.hudson-ci.org/browse/HUDSON-9008 HUDSON-9002: hudson.util.IOException2 in hudson.model.Api.doXml http://issues.hudson-ci.org/browse/HUDSON-9002
(In reply to comment #10) > One concern I have with the latest Hudson 2.1.1 release are these bugs which > break the Gerrit Trigger plug-in (not sure if EGit is using that) and causes > errors in the XML REST interface for jobs hosted in Git: > Well the sandbox is running 2.1.0 and I haven't had any problems reported by the Egit team(they have a Gerrit trigger setup there) so I think we're ok. -M.
The Gerrit Trigger plug-in breaks when updating to 2.1.1 (2.1.0 is still okay). A possible work around is to install the latest Jenkins Gerrit Trigger plug-in.
Hudson 2.1.2 fixes the compatibility problem with Mylyn mentioned in comment 10 so no more concerns from my end.
Ok, well at this time my plan is to upgrade to 2.1.0 on monday morning. -M.
Well the upgrade went well, however we seem to be having some slight stability issues(due to OOM events). I'm going to close this as 'fixed' since the the upgrade is done. -M.
I have filed bug 360691 for updating to Hudson 2.1.2.
