Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Hudson job stuck

Actually, the problem is more widespread. We have more than one job with the virgo-serialise lock showing as running concurrently in the executor queue. See the attached screenshot. Only the kernel's blue ball is flashing, but the build executor status shows a few Virgo jobs running. (Perhaps the lock is implemented by creating jobs and having them contend for the lock, but that would be a bit of a strange way to implement serialisation as it would chew up more processes than necessary.)

There is other weirdness. The progress bar of the artifact repository job 752 below, when hovered over, says "Started null ago. Estimated time remaining: null." - please see the second screenshot. I've raised a Hudson bug 390314 to capture this as it may be straightforward to diagnose and fix.

So perhaps it's time for a restart?

Regards,
Glyn

On 25 Sep 2012, at 10:46, Glyn Normington wrote:

Dear Web Master

I would be grateful if you could kill the following job, or recycle enough of Hudson to kill it:

https://hudson.eclipse.org/hudson/view/Virgo/job/virgo.artifact-repository.snapshot/752/

We've tried multiple times and it won't die.

Thanks.

Regards,
Glyn


Back to the top