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

Report project which caused dead executor thread

    XMLWordPrintable

Details

    Description

      The error message is reported if the nextBuildNumber is lower than the current build number:

      hudson.model.Executor#run: Unexpected executor death
      java.lang.IllegalStateException: cannot create a build with number NUMBER since that (or higher) is already in use among [NUMBER]
      

      Unfortunately this does not report the actual project which is hitting the issue, so it is difficult to determine which project(s) need to be fixed.

      You can easily reproduce this problem by triggering 3 builds and manually setting the nextBuildNumber file to be 1. Triggering a new build will kill the build executor thread.

      Attachments

        Activity

          godfath3r Panagiotis Galatsanos added a comment - - edited

          The issue is not reproducible at least on Jenkins 2.73.

          Changing the nextBuildNumber is handled by Jenkins, and you get this message:

          WARNING: JENKINS-27530: improper nextBuildNumber 1 detected in hudson.model.FreeStyleProject@c4bd16a[JOB_NAME] with highest build number 4; adjusting

          Is there any other way to reproduce it?

          Maybe this patch can help the error message to be more informative in case of unexpected executor death.

          https://github.com/jenkinsci/jenkins/pull/2970

          godfath3r Panagiotis Galatsanos added a comment - - edited The issue is not reproducible at least on Jenkins 2.73. Changing the nextBuildNumber is handled by Jenkins, and you get this message: WARNING: JENKINS-27530 : improper nextBuildNumber 1 detected in hudson.model.FreeStyleProject@c4bd16a [JOB_NAME] with highest build number 4; adjusting Is there any other way to reproduce it? Maybe this patch can help the error message to be more informative in case of unexpected executor death. https://github.com/jenkinsci/jenkins/pull/2970
          oleg_nenashev Oleg Nenashev added a comment -

          The fix has been integrated towards Jenkins 2.74. Marking as LTS Candidate

          oleg_nenashev Oleg Nenashev added a comment - The fix has been integrated towards Jenkins 2.74. Marking as LTS Candidate
          jglick Jesse Glick added a comment -

          I do not think the linked patch would assist in reproducing at all. The name of the executor thread is irrelevant. The question is why nextBuildNumber got corrupted. lts-candidate is not appropriate.

          jglick Jesse Glick added a comment - I do not think the linked patch would assist in reproducing at all. The name of the executor thread is irrelevant. The question is why nextBuildNumber got corrupted. lts-candidate is not appropriate.
          jglick Jesse Glick added a comment -

          Too late I guess.

          jglick Jesse Glick added a comment - Too late I guess.

          People

            godfath3r Panagiotis Galatsanos
            schristou Steven Christou
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: