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

timer expires, and build is halted, but build is not marked as failed

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • build-timeout-plugin
    • None
    • Debian Lenny, Jenkins ver. 1.404 and build-timeout ver. 1.7

      I just installed the build-timeout plugin and it's mostly working, but
      even with the "Fail the build" setting checked, my builds are still
      being marked as "aborted":

      For example, here is the tail of the console output:
      {{
      [...]
      Build timed out (after 3 minutes). Marking the build as failed.
      Terminated
      +++ vncserver -kill beast:3 -clean
      Killing Xtightvnc process ID 12328
      +++ exit
      Finished: ABORTED
      }}

      Note that it says it will fail the build, but then it is aborted and
      the status of the build is set to aborted, not failed. Bonus pain:
      Of course no email goes out.

      This is with Jenkins ver. 1.404 and build-timeout ver. 1.7.

          [JENKINS-9203] timer expires, and build is halted, but build is not marked as failed

          Eric Engstrom created issue -
          Eric Engstrom made changes -
          Description Original: I just installed the build-timeout plugin and it's mostly working, but
          even with the "Fail the build" setting checked, my builds are still
          being marked as "aborted":

          For example, here is the tail of the console output:
          {{
          [...]
          Build timed out (after 3 minutes). Marking the build as failed.
          Terminated
          +++ vncserver -kill beast:3 -clean
          Killing Xtightvnc process ID 12328
          +++ exit
          Finished: ABORTED
          }}

          Note that it says it will fail the build, but then it is aborted and
          the status of the build is set to aborted, not failed. Bonus pain:
          Of course no email goes out.

          This is with Jenkins ver. 1.401 and build-timeout ver. 1.7.




          New: I just installed the build-timeout plugin and it's mostly working, but
          even with the "Fail the build" setting checked, my builds are still
          being marked as "aborted":

          For example, here is the tail of the console output:
          {{
          [...]
          Build timed out (after 3 minutes). Marking the build as failed.
          Terminated
          +++ vncserver -kill beast:3 -clean
          Killing Xtightvnc process ID 12328
          +++ exit
          Finished: ABORTED
          }}

          Note that it says it will fail the build, but then it is aborted and
          the status of the build is set to aborted, not failed. Bonus pain:
          Of course no email goes out.

          This is with Jenkins ver. 1.404 and build-timeout ver. 1.7.




          Environment Original: Debian Lenny New: Debian Lenny, Jenkins ver. 1.404 and build-timeout ver. 1.7

          jlpinardon added a comment - - edited

          And also, if a build is configured to be triggered when the "timed out" build is failed, the build is not triggered.

          Our Configuration :
          Hudson Master SUN OS 10
          Java 1.6.0.18
          Jenkins 1.404
          Build Timeout 1.7

          Hudson Slave :
          Linux RH5
          java 1.6.0_21-b06

          A Test done with a Hudson 1.395 and BuildTimeOut 1.6 shows that it was OK with these couple of version.

          jlpinardon added a comment - - edited And also, if a build is configured to be triggered when the "timed out" build is failed, the build is not triggered. Our Configuration : Hudson Master SUN OS 10 Java 1.6.0.18 Jenkins 1.404 Build Timeout 1.7 Hudson Slave : Linux RH5 java 1.6.0_21-b06 A Test done with a Hudson 1.395 and BuildTimeOut 1.6 shows that it was OK with these couple of version.
          jlpinardon made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

          redsolo added a comment -

          Im seeing this as well. Jenkins 1.404, build-timeout plugin 1.7.

          java.runtime.name Java(TM) SE Runtime Environment 1.6.0_24-b07
          java.vm.name Java HotSpot(TM) 64-Bit Server VM
          os.arch amd64
          os.name Linux
          os.version 2.6.18-238.1.1.el5

          Output at the end of the log:

          Build timed out (after 15 minutes). Marking the build as failed.
          Finished: ABORTED
          

          redsolo added a comment - Im seeing this as well. Jenkins 1.404, build-timeout plugin 1.7. java.runtime.name Java(TM) SE Runtime Environment 1.6.0_24-b07 java.vm.name Java HotSpot(TM) 64-Bit Server VM os.arch amd64 os.name Linux os.version 2.6.18-238.1.1.el5 Output at the end of the log: Build timed out (after 15 minutes). Marking the build as failed. Finished: ABORTED

          redsolo added a comment -

          This bug was introduced in Jenkins version 1.398. 1.397 works fine, but 1.398-404 doesnt. I dont know how to fix it, but I have created an integration test case to show the problem in 1.398+.

          redsolo added a comment - This bug was introduced in Jenkins version 1.398. 1.397 works fine, but 1.398-404 doesnt. I dont know how to fix it, but I have created an integration test case to show the problem in 1.398+.

          The LTS(RC) version Jenkins ver. 1.400.1-SNAPSHOT (private-05/12/2011 11:17-kohsuke). Downloaded today do have the same issue. If the fix has low risk a back port of it the coming fix would be appreciated

          Asmund Ostvold added a comment - The LTS(RC) version Jenkins ver. 1.400.1-SNAPSHOT (private-05/12/2011 11:17-kohsuke). Downloaded today do have the same issue. If the fix has low risk a back port of it the coming fix would be appreciated

          This regression was induced by 9c965617b3b385ef65eaf50860865c05a114a01d which refers to JENKINS-7864 and JENKINS-8054. Still investigating.

          Kohsuke Kawaguchi added a comment - This regression was induced by 9c965617b3b385ef65eaf50860865c05a114a01d which refers to JENKINS-7864 and JENKINS-8054 . Still investigating.

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          changelog.html
          core/src/main/java/hudson/matrix/MatrixBuild.java
          core/src/main/java/hudson/model/Build.java
          core/src/main/java/hudson/model/Executor.java
          core/src/main/java/hudson/model/Result.java
          core/src/main/java/hudson/model/Run.java
          maven-plugin/src/main/java/hudson/maven/Maven3Builder.java
          maven-plugin/src/main/java/hudson/maven/MavenBuilder.java
          maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
          test/src/test/java/hudson/model/AbortedFreeStyleBuildTest.java
          http://jenkins-ci.org/commit/jenkins/a3354b12cfc5f554487b59f35e5a0bdbce8861a6
          Log:
          [FIXED JENKINS-9203] in light of 9c965617b3b385ef65eaf50860865c05a114a01d, I think the proper fix is to define a mechanism to abort with status.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/matrix/MatrixBuild.java core/src/main/java/hudson/model/Build.java core/src/main/java/hudson/model/Executor.java core/src/main/java/hudson/model/Result.java core/src/main/java/hudson/model/Run.java maven-plugin/src/main/java/hudson/maven/Maven3Builder.java maven-plugin/src/main/java/hudson/maven/MavenBuilder.java maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java test/src/test/java/hudson/model/AbortedFreeStyleBuildTest.java http://jenkins-ci.org/commit/jenkins/a3354b12cfc5f554487b59f35e5a0bdbce8861a6 Log: [FIXED JENKINS-9203] in light of 9c965617b3b385ef65eaf50860865c05a114a01d, I think the proper fix is to define a mechanism to abort with status.
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            kohsuke Kohsuke Kawaguchi
            eengstrom Eric Engstrom
            Votes:
            9 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: