jenkinsci / jenkinsci/workflow-basic-steps-plugin

[JENKINS-38713] timeout failing to terminate run-away Pipeline executions

Open
#408 0 comments 0 reactions 0 assignees View on GitHub
component:workflow-basic-steps-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
73
Forks
129
PR merge metrics
No merged PRs in 30d

Description

In this Jenkinsfile we're using a timeout block to prevent run-away test executions which would waste our cloud budget.

It appears that this fails to actually stop executions.in some circumstances that I have not yet determined.

I captured the following thread-dump from the Pipeline execution:

Thread #12

at DSL.sh(awaiting process completion in /home/azureuser/workspace/Core_jenkins_upstream-XZUSMW3CKUAM6W5W2KS46X6N7A3DSFZYKUTDXGXOKZVL3XWWFAMA@​tmp/durable-56765fdf on Azure1003041313 (pid: 65350))
at WorkflowScript.run(WorkflowScript:39)
at WorkflowScript.withMavenEnv(WorkflowScript:76)
at DSL.withEnv(Native Method)
at WorkflowScript.withMavenEnv(WorkflowScript:75)
at WorkflowScript.run(WorkflowScript:33)
at DSL.timeout(Native Method)
at WorkflowScript.run(WorkflowScript:30)
at DSL.stage(Native Method)
at WorkflowScript.run(WorkflowScript:29)
at DSL.timestamps(Native Method)
at WorkflowScript.run(WorkflowScript:21)
at DSL.node(running on Azure1003041313)
at WorkflowScript.run(WorkflowScript:20)

I don't yet have a reproduction case, as I see this only sporadically, but I see it at least once or twice a week on ci.jenkins.io so if there are additional diagnostics I can perform the next time I see the issue, please let me know!

---
Originally reported by rtyler, imported from: timeout failing to terminate run-away Pipeline executions


  • assignee: cloudbees
  • status: Open
  • priority: Minor
  • component(s): workflow-basic-steps-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 2
  • imported: 20251215-220547

Raw content of original issue

In this Jenkinsfile we're using a timeout block to prevent run-away test executions which would waste our cloud budget.

It appears that this fails to actually stop executions.in some circumstances that I have not yet determined.

I captured the following thread-dump from the Pipeline execution:


Thread #12

at DSL.sh(awaiting process completion in /home/azureuser/workspace/Core_jenkins_upstream-XZUSMW3CKUAM6W5W2KS46X6N7A3DSFZYKUTDXGXOKZVL3XWWFAMA@tmp/durable-56765fdf on Azure1003041313 (pid: 65350))
at WorkflowScript.run(WorkflowScript:39)
at WorkflowScript.withMavenEnv(WorkflowScript:76)
at DSL.withEnv(Native Method)
at WorkflowScript.withMavenEnv(WorkflowScript:75)
at WorkflowScript.run(WorkflowScript:33)
at DSL.timeout(Native Method)
at WorkflowScript.run(WorkflowScript:30)
at DSL.stage(Native Method)
at WorkflowScript.run(WorkflowScript:29)
at DSL.timestamps(Native Method)
at WorkflowScript.run(WorkflowScript:21)
at DSL.node(running on Azure1003041313)
at WorkflowScript.run(WorkflowScript:20)

I don't yet have a reproduction case, as I see this only sporadically, but I see it at least once or twice a week on ci.jenkins.io so if there are additional diagnostics I can perform the next time I see the issue, please let me know!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.