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

ISE from RunMap.put using /git/notifyCommit on a matrix project

      Jan 23, 2015 11:43:52 PM hudson.model.Executor run
      SEVERE: Unexpected executor death
      java.lang.IllegalStateException: /MY_DIR/jenkins/home/jobs/MY_JOB/builds/29 already existed; will not overwite with MY_JOB #29
      at hudson.model.RunMap.put(RunMap.java:187)
      at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178)
      at hudson.model.AbstractProject.newBuild(AbstractProject.java:1001)
      at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1200)
      at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
      at hudson.model.Executor.run(Executor.java:213)

      I tried to manually start a job via the run button. I see the Dead indicator in the executor status sidebar. I was able to restart the thread and then manually start the job again. This time it started with #30 and appears to be running OK.

      Looking at JENKINS_HOME dir in linux, I see that there is a build directory for #29 and the job ran and failed (unrelated). Looking at the Jenkins webpage for the job, the build skips from 28 to (the now running) 30. #29 has no listing.

      I know some items related to the major enhancement are not closed yet, like JENKINS-23152, so please close this if the behavior I'm seeing is expected until the next release. If this is unexpected - hopefully this report is informative - this issue happened 4x in a row for each job I had put in the build queue.

        1. screenshot-3.png
          32 kB
          philbeiler
        2. screenshot-2.png
          15 kB
          philbeiler
        3. screenshot-1.png
          16 kB
          philbeiler
        4. config.xml
          5 kB
          Mark Sinclair

          [JENKINS-26582] ISE from RunMap.put using /git/notifyCommit on a matrix project

          Mark Sinclair created issue -
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-24380 [ JENKINS-24380 ]

          Daniel Beck added a comment -

          This may be a legitimate bug revealed by the changes for JENKINS-24380 (I actually asked for this to be an error condition to prevent overriding existing builds).

          Are you using Gerrit Trigger Plugin?

          Is there a build.xml in 29 (while Jenkins still thinks the next build should be 29)?

          Daniel Beck added a comment - This may be a legitimate bug revealed by the changes for JENKINS-24380 (I actually asked for this to be an error condition to prevent overriding existing builds). Are you using Gerrit Trigger Plugin? Is there a build.xml in 29 (while Jenkins still thinks the next build should be 29)?

          Mark Sinclair added a comment -

          Gerrit Trigger Plugin is not installed.

          Yes, there is a build.xml for build29.

          Mark Sinclair added a comment - Gerrit Trigger Plugin is not installed. Yes, there is a build.xml for build29.

          Daniel Beck added a comment -

          Does Jenkins show a build 29 that corresponds with the builds/29/build.xml file? Or does it stop at build 28?

          Daniel Beck added a comment - Does Jenkins show a build 29 that corresponds with the builds/29/build.xml file? Or does it stop at build 28?

          Mark Sinclair added a comment -

          On the Jenkins project web page, I see all builds through 28, 29 is missing, and then I see build 30.
          In Linux JENKINS_HOME/jobs/MY_JOB/builds/ shows all builds, including 29.

          Mark Sinclair added a comment - On the Jenkins project web page, I see all builds through 28, 29 is missing, and then I see build 30. In Linux JENKINS_HOME/jobs/MY_JOB/builds/ shows all builds, including 29.

          Daniel Beck added a comment -

          What kind of projects (e.g. Freestyle, Maven, Matrix) are affected?

          When you restart Jenkins, does build 29 appear afterwards?

          Daniel Beck added a comment - What kind of projects (e.g. Freestyle, Maven, Matrix) are affected? When you restart Jenkins, does build 29 appear afterwards?
          Mark Sinclair made changes -
          Attachment New: config.xml [ 28419 ]

          Mark Sinclair added a comment -

          After soft restart of Jenkins, the missing build re-appears (#29).

          All projects are freestyle. I attached my config.xml as well if that will help (replaced some fields with XXX).

          Mark Sinclair added a comment - After soft restart of Jenkins, the missing build re-appears (#29). All projects are freestyle. I attached my config.xml as well if that will help (replaced some fields with XXX).

          Jesse Glick added a comment -

          The only suspicious thing I see in the job config is the use of the Heavy Job plugin. Is this problem at all reproducible for you? If so, does skipping use of Heavy Job fix it?

          The critical diagnostic which was not mentioned here was whether nextBuildNumber existed and if so what it said. It is supposed to point to the next build number which should be created. If for some reason it failed to be updated, Jenkins would try to recreate a build with the same number. In the past this mistake would have resulted in an earlier build being silently overwritten. As of 1.597 it is caught.

          The same applies to bugs like JENKINS-23152, with a different cause (objects held in memory with stale contents).

          Jesse Glick added a comment - The only suspicious thing I see in the job config is the use of the Heavy Job plugin. Is this problem at all reproducible for you? If so, does skipping use of Heavy Job fix it? The critical diagnostic which was not mentioned here was whether nextBuildNumber existed and if so what it said. It is supposed to point to the next build number which should be created. If for some reason it failed to be updated, Jenkins would try to recreate a build with the same number. In the past this mistake would have resulted in an earlier build being silently overwritten. As of 1.597 it is caught. The same applies to bugs like JENKINS-23152 , with a different cause (objects held in memory with stale contents).

            jglick Jesse Glick
            msinclair Mark Sinclair
            Votes:
            6 Vote for this issue
            Watchers:
            22 Start watching this issue

              Created:
              Updated:
              Resolved: