Repository navigation
[JENKINS-2618] Mis-reporting hung build #14088
Description
"If a build appears to be hanging for too long, Hudson turns the progress bar to
red"
My expectation would be that this wouldn't happen unless the job was actively
building.
Currently jobs sitting in the build queue will turn read and indicate that they
might be stuck, which is not the case... they are just waiting for an open build
executor to begin building.
Originally reported by brucepainter, imported from: Mis-reporting hung build
- status: Closed
- priority: Major
- component(s): core
- resolution: Fixed
- resolved: 2008-11-17T17:05:09+00:00
- votes: 0
- watchers: 0
- imported: 2025-11-24
Raw content of original issue
"If a build appears to be hanging for too long, Hudson turns the progress bar to red"
My expectation would be that this wouldn't happen unless the job was actively building.
Currently jobs sitting in the build queue will turn read and indicate that they might be stuck, which is not the case... they are just waiting for an open build executor to begin building.
- environment:
Platform: PC, OS: Linux
Activity
jenkins-infra-bot commentedon Nov 16, 2008
Raw content of original comment:
This is also by design — if a job is sitting in a queue for "too long" (which
means twice the build time of the job), it's marked as stuck.
I think this is too aggressive, so I changed it to 10x the build time in 1.263.
The goal of this feature to let you know that you'll be better off if you add
more slaves.
jenkins-infra-bot commentedon Nov 17, 2008
Raw content of original comment:
Code changed in hudson
User: : kohsuke
Path:
trunk/hudson/main/core/src/main/java/hudson/model/Queue.java
http://fisheye4.cenqua.com/changelog/hudson/?cs=13272
Log:
[FIXED] relaxed the delay factor based on the feedback in
JENKINS-2618. In 1.263.