Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33763

Timeout seems to fail to kill job.

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Labels:
      None
    • Environment:
      Windows Server 2012R2, Swarm client 2.0, Debian server, running docker, running Jenkins 1.643.
    • Similar Issues:

      Description

      I have the following simple timeout workflow and running it, with no luck actually killing the job.

      Started by user Tilander, Jim
      [Pipeline] Allocate node : Start
      Running on CT-COMPASS-W63-15f9431a in c:\jenkins\small\workspace\pipeline-testbed
      [Pipeline] node {
      [Pipeline] stage (Stage 1)
      Entering stage Stage 1
      Proceeding
      [Pipeline] Enforce time limit : Start
      [Pipeline] timeout {
      [Pipeline] bat
      [pipeline-testbed] Running batch script

      c:\jenkins\small\workspace\pipeline-testbed>ping -t 8.8.8.8

      Pinging 8.8.8.8 with 32 bytes of data:
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Sending interrupt signal to process
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53
      Reply from 8.8.8.8: bytes=32 time=1ms TTL=53

      I'm running on Windows Server 2012R2, with the Swarm client:

      http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/swarm-client/2.0/

      This is the script:

      node {
      stage 'Stage 1'
      timeout(time: 13, unit: 'SECONDS')

      { bat 'ping -t 8.8.8.8' }

      stage 'Stage 2'
      echo 'Hello World 2'
      }

        Attachments

          Activity

          Hide
          jglick Jesse Glick added a comment -

          Update all Pipeline-related plugins and check the virtual thread dump.

          Show
          jglick Jesse Glick added a comment - Update all Pipeline-related plugins and check the virtual thread dump.

            People

            • Assignee:
              kohsuke Kohsuke Kawaguchi
              Reporter:
              jtilander Jim Tilander
            • Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: