|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Noticed this recently after an upgrade, and might be related, running 1.602
Reported here rather than
JENKINS-26739since it's already closed and this bug relates more to RunMap.put rather than lazyput. The matrix build below has one configuration runs on one node with 1 executor so concurrency here shouldn't be an issue.I get:
Mar 11, 2015 4:07:24 PM hudson.plugins.git.GitStatus$JenkinsAbstractProjectListener onNotifyCommit
INFO: Scheduling MY_JOB to build commit MY_ID
Mar 11, 2015 4:07:24 PM hudson.plugins.git.GitStatus$JenkinsAbstractProjectListener onNotifyCommit
INFO: Scheduling MY_JOB ยป MY_HOST to build commit MY_ID
Mar 11, 2015 4:07:24 PM hudson.model.Executor run
SEVERE: Unexpected executor death
java.lang.IllegalStateException: /MY_DIR/jobs/MY_JOB/builds/20 already existed; will not overwite with MY_JOB
/label=MY_JOB #20
at hudson.model.RunMap.put(RunMap.java:187)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)
I get this almost every triggered build. Manually restarting the thread sees the build succeed.
Interestingly, on the filesystem I see build 21 already exists when it fails:
MY_DIR/jobs/MY_JOB/builds$ ls -lR 20 21 ../nextBuildNumber
rw-rr- 1 jenkins jenkins 3 Mar 11 16:07 ../nextBuildNumber20:
total 16
rw-rr- 1 jenkins jenkins 6488 Mar 11 14:11 build.xmlrw-rr- 1 jenkins jenkins 478 Mar 11 14:04 changelog.xmlrw-rr- 1 jenkins jenkins 2424 Mar 11 14:11 log21:
total 8
rw-rr- 1 jenkins jenkins 1723 Mar 11 16:07 changelog.xmlrw-rr- 1 jenkins jenkins 2110 Mar 11 16:08 logMY_DIR/jobs/MY_JOB/builds$ cat ../nextBuildNumber
22
Job 20 shows up in the gui as completed, job 21 still running (executor crashed)
So it looks like the wrong build number is being picked up (note the times of build 21 and the log message 4:07)