On Wed, Nov 20, 2013 at 05:39:35PM -0600, Ken Causey wrote:
I would really appreciate it if someone with Jenkins expertise would look at the situation with build.squeak.org (aka box3). Multiple jobs are stuck and some date back to the 17th. I would just kill them but it seems to me the problem will be right back in a matter of hours or no more than a day. If nothing else maybe the problem job(s) can simply be suspended temporarily.
Ken
I don't know the underlying problem, but there were lots of ruby and squeakvm processes reparented to root, and no clear indication of what is going wrong. I killed off as many of the reparented processes as I could find.
Currently there is one Jenkins job running, and one squeakvm process corresponding to that job. I'll look again in a day or so and see how many runaway processes may have come back.
Dave