-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.144 on Linux, Java 8.
We have a pipeline job that intermittently hangs forever right at the end of the job.
Here's what the console log looks like
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Ongoing user visit)
[Pipeline] script
[Pipeline] {
[Pipeline] readFile
[Pipeline] fileExists
[Pipeline] fileExists
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Check data age)
[Pipeline] fileExists
[Pipeline] script
[Pipeline] {
[Pipeline] fileExists
[Pipeline] readFile
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv <-- stuck at this point until I aborted the job
Aborted by Matthew Webber (<userid>)
Click here to forcibly terminate running steps
Terminating node
Click here to forcibly kill entire build
Hard kill!
Finished: ABORTED
I've attached 4 thread dumps, as follows:
Thread dumps from both the master, and the agent:
http://jenkins.somewhere.com:8080/threadDump http://jenkins.somewhere.com:8080/computer/g18-sc-serv-04/systemInfo
1,2 - Thread dumps at the point when the job was hung
3,4 - Thread dumps at the point where I have aborted the job, and then clicked Click here to forcibly terminate running steps, and the console log was saying Terminating node.
None of the thread dumps show anything for the jobname that was hung EM_checkstatus_m03, which suggests that at least part of Jenkins though the job had finished.
