-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Trivial
-
Resolution: Unresolved
-
Component/s: core, workflow-cps-plugin, workflow-job-plugin
-
Labels:
-
Similar Issues:
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
-
- Open
-
- links to
Devin Nusbaum unfortunately, I don't. I've got a few 1000+ LOC pipelines running continuously. I do not know how to tell which one leaves executors and when.
Pipeline build that has such "likelyStuck" executor looks completed on its build page (no progress bars, build status is set). But I still can see a matching OneOffExecutor on master: