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
-
JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume
-
- Resolved
-
- relates to
-
JENKINS-53158 Pipelines leak OneOffExecutors when triggered on a temporary offline master
-
- Resolved
-
-
JENKINS-60348 Followup - Investigate root cause of idle executors
-
- Open
-
-
JENKINS-61087 Use FlowExecutionList to calculate the number of running Pipeline jobs
-
- Resolved
-
- links to
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.