Details
-
Bug
-
Status: Open (View Workflow)
-
Trivial
-
Resolution: Unresolved
Description
I doubt this one is reproductible.
Going to yourjiraurlhere/computer/api/json?pretty=true&tree=computer[oneOffExecutors[likelyStuck,currentExecutable[result,url]]]{0}
gives you the jobs currently running.
One of my job is marked as "likely stuck", but his state is result is "SUCCESS" (and has been "SUCCESS" since 2h30, making me doubt about the veracity of the "likely stuck".
The job isn't running either. It's completed, but is still somehow showing as "likely stuck".
Attachments
Issue Links
- is related to
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
JENKINS-60348 Followup - Investigate root cause of idle executors
-
- Open
-
-
-
- Resolved
-
- links to
Activity
gives you the jobs currently running
This is not really an appropriate API query to use for that question. If your interest is limited to all Pipeline builds, FlowExecutionList is likely to be more useful. If you are looking at builds of a particular job (Pipeline or not), I think that information is available from the endpoint for that job.
TCP prevents scheduling more builds because it considers those hanging executors.
Offhand this sounds like a flaw in TCB. This PR introduced that behavior, purportedly to support the build-flow plugin (a conceptual predecessor of Pipeline née Workflow). If TCB intends to throttle builds per se (rather than work done by those builds—typically node blocks for Pipeline), then there are more direct ways of doing this than counting Executor slots.
Basil Crow
added a comment - Offhand this sounds like a flaw in TCB.
I am attempting to fix this flaw in jenkinsci/throttle-concurrent-builds-plugin#57.
Basil Crow
added a comment - Offhand this sounds like a flaw in TCB.
I am attempting to fix this flaw in jenkinsci/throttle-concurrent-builds-plugin#57 . Basil Crow
added a comment - I am attempting to fix this flaw in jenkinsci/throttle-concurrent-builds-plugin#57.
This PR has been merged, and the master branch of Throttle Concurrent Builds now uses FlowExecutionList to calculate the number of running Pipeline jobs, which should work around the issue described in this bug. I have yet to release a new version of Throttle Concurrent Builds with this fix, but there is an incremental build available here. atikhonova, are you interested in testing this incremental build before I do an official release?
Basil Crow
added a comment - I am attempting to fix this flaw in jenkinsci/throttle-concurrent-builds-plugin#57 .
This PR has been merged, and the master branch of Throttle Concurrent Builds now uses FlowExecutionList to calculate the number of running Pipeline jobs, which should work around the issue described in this bug. I have yet to release a new version of Throttle Concurrent Builds with this fix, but there is an incremental build available here . atikhonova , are you interested in testing this incremental build before I do an official release? 
atikhonova Are you able upload the build directory of the build matching the stuck executor? Specifically, it would be helpful to see build.xml and the xml file(s) in the workflow directory. EDIT: I see now that you can't easily tell which are stuck and which are good. If you can find an executor with likelyStuck: true, and whose build looks like it has otherwise completed or is suck, that would be a great candidate.
Another note:
JENKINS-38381will change the control flow here significantly.