-
Bug
-
Resolution: Unresolved
-
Trivial
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".
- 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