jenkinsci / jenkinsci/workflow-basic-steps-plugin

[JENKINS-58752] Timeout with activity: true and activity timed out

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

Description

My pipeline has the following options:

  options {

buildDiscarder(logRotator(numToKeepStr: '3'))
disableResume()
timeout(activity: true, time: 10, unit: 'MINUTES')
}

However, there is sometimes a timeout, although every few seconds the log is extended. In the case the log says:

```
Timeout set to expire after 10 min without activity
...
Cancelling nested steps due to timeout
Sending interrupt signal to process
...
Timeout has been exceeded
```

The timeout occurs always in the Test Stage, during a nightwatch test. The position seems not deterministic. I have 4 nightwatch tests in this stage and I got timeouts at the beginning and also at the end of this stage.

Sometimes the pipeline works as it should and after about 16 minutes the build is completed successfully.

I also changed the timeout time (e.g. 2,3,5,15 minutes) and got similar results.

 

---
Originally reported by mikorn, imported from: Timeout with activity: true and activity timed out


  • status: Open
  • priority: Major
  • component(s): workflow-basic-steps-plugin
  • resolution: Unresolved
  • votes: 7
  • watchers: 16
  • imported: 20251215-220547

Raw content of original issue

My pipeline has the following options:



  options {

buildDiscarder(logRotator(numToKeepStr: '3'))
disableResume()
timeout(activity: true, time: 10, unit: 'MINUTES')
}


However, there is sometimes a timeout, although every few seconds the log is extended. In the case the log says:



Timeout set to expire after 10 min without activity

...
Cancelling nested steps due to timeout
Sending interrupt signal to process
...
Timeout has been exceeded


The timeout occurs always in the Test Stage, during a nightwatch test. The position seems not deterministic. I have 4 nightwatch tests in this stage and I got timeouts at the beginning and also at the end of this stage.

Sometimes the pipeline works as it should and after about 16 minutes the build is completed successfully.
I also changed the timeout time (e.g. 2,3,5,15 minutes) and got similar results.

 

environment

```
Jenkins ver. 2.176.2

Basic Steps 2.18

Job running on a Windows Slave connected with JNLP4
```

1 attachment

- [Screen Shot 2021-04-21 at 16.50.07.png](https://issues.jenkins.io/secure/attachment/54645/Screen%20Shot%202021-04-21%20at%2016.50.07.png)
> ![Screen Shot 2021-04-21 at 16.50.07.png](https://issues.jenkins.io/secure/attachment/54645/Screen%20Shot%202021-04-21%20at%2016.50.07.png)

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.