[JIRA] [core] (JENKINS-26582) ISE from RunMap.put after reloading config

6 views
Skip to first unread message

philbeiler@java.net (JIRA)

unread,
May 7, 2015, 3:20:01 PM5/7/15
to jenkinsc...@googlegroups.com
philbeiler commented on Bug JENKINS-26582
 
Re: ISE from RunMap.put after reloading config

Just curious if this is being actively worked or if there is any kind of timeline for resolution? This has completely killed my environment, as all of our jobs are Matrix builds (with automated feature branch/job creation and web hook pushes from GIT to kick off the jobs). Within an hour, all nodes on our farm are full of dead threads – Jenkins is basically down and unusable... serious bummer!

Are there any work-arounds? Or do I have to change all of my jobs to polling and give up on the hooks? Thanks for any information.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

jglick@cloudbees.com (JIRA)

unread,
May 7, 2015, 3:48:01 PM5/7/15
to jenkinsc...@googlegroups.com

This is not being actively worked on because there is no known way to reproduce from scratch.

I did file a PR to downgrade the error to a warning, closer to the pre-1.597 state (which allowed builds to be overwritten silently), but it was rejected. No problem to reopen that discussion, though of course providing developers with a way to reproduce the problem would be far better.

daniel@beckweb.net (JIRA)

unread,
May 7, 2015, 4:00:02 PM5/7/15
to jenkinsc...@googlegroups.com

Would be great if we knew how to reproduce this. Not something vague, but full steps to reproduce on a newly set up instance. If you're experiencing this issue, consider spinning up a second Jenkins instance (could be your desktop machine) to try to make this reproducible based on what you know about your production instance. Only once we know the circumstances for this to happen, we can investigate them and fix the underlying problem.

philbeiler@java.net (JIRA)

unread,
May 8, 2015, 6:58:01 AM5/8/15
to jenkinsc...@googlegroups.com
philbeiler updated an issue
 
Jenkins / Bug JENKINS-26582
Change By: philbeiler
Attachment: screenshot-1.png

philbeiler@java.net (JIRA)

unread,
May 8, 2015, 7:18:04 AM5/8/15
to jenkinsc...@googlegroups.com
philbeiler updated an issue
Change By: philbeiler
Attachment: screenshot-2.png

philbeiler@java.net (JIRA)

unread,
May 8, 2015, 7:20:03 AM5/8/15
to jenkinsc...@googlegroups.com
philbeiler commented on Bug JENKINS-26582
 
Re: ISE from RunMap.put after reloading config

Fortunately, I was able to easily duplicate the problem in about 5 minutes, first crack! Hopefully you can too!

Ubuntu 15.04 - Does not matter, not what I'm running in prod
Jenkins 1.612 - Does not matter, not what I'm running in prod – seems like this problem started around 1.597??? Not really sure when.
Install Git Plugin
Two slaves s1 and s2 both on localhost - each with 2 executors s1 label S1, s2 label with S2 (I run no executors on master in prod, just an FYI)
Create a Matrix job
GIT REPO https://github.com/allegro/axion-release-plugin.git (use this repo, as I'm using a hash for this repository - no auth required )
Branches to build: origin/master
Additional Behavoir -> Local Branch Name: master
Schedule: H 0 1 1 0
Configuration Matrix Label Expression label_exp S1 S2

Build Execute Shell Command echo "--------------->"$label_exp

Per the gentleman's comment above – simply post this url in another browser tab and watch your threads die... Keep submitting, and they all die...

http://localhost:8080/jenkins//git/notifyCommit?url=https%3A%2F%2Fgithub.com%2Fallegro%2Faxion-release-plugin.git&branches=master&sha1=a5de4d725814ff907a8cf1f5666b9f01e8361655

SEVERE: Unexpected executor death
java.lang.IllegalStateException: /usr/share/tomcat8/.jenkins/jobs/test/configurations/axis-label_exp/S1/builds/3 already existed; will not overwite with test/label_exp=S1 #3
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor$1.call(Executor.java:328)
at hudson.model.Executor$1.call(Executor.java:310)
at hudson.model.Queue._withLock(Queue.java:1251)
at hudson.model.Queue.withLock(Queue.java:1189)
at hudson.model.Executor.run(Executor.java:310)

Let me know if this does not work, or you want some config files. I hope it is easily reproducible..and quickly resolved – this is killing me! Thanks so much for your help...

This is even worse.. I lose my node after a while – I saw this in product and but I did not think it was related...

No I have these messages in the log...

May 08, 2015 7:15:45 AM hudson.triggers.SafeTimerTask run
SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@7c2aef8c failed
java.lang.NullPointerException
at hudson.model.LoadStatistics$LoadStatisticsSnapshot$Builder.with(LoadStatistics.java:624)
at hudson.model.LoadStatistics$LoadStatisticsSnapshot$Builder.with(LoadStatistics.java:619)
at hudson.model.LoadStatistics.computeSnapshot(LoadStatistics.java:352)
at hudson.model.LoadStatistics.computeSnapshot(LoadStatistics.java:332)
at hudson.slaves.NodeProvisioner$2.run(NodeProvisioner.java:261)
at hudson.model.Queue._withLock(Queue.java:1212)
at hudson.model.Queue.withLock(Queue.java:1148)
at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:208)
at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:57)
at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:778)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

May 08, 2015 7:15:51 AM hudson.triggers.SafeTimerTask run
SEVERE: Timer task hudson.model.LoadStatistics$LoadStatisticsUpdater@40623d93 failed
java.lang.NullPointerException
at hudson.model.LoadStatistics$LoadStatisticsSnapshot$Builder.with(LoadStatistics.java:624)
at hudson.model.LoadStatistics$LoadStatisticsSnapshot$Builder.with(LoadStatistics.java:619)
at hudson.model.LoadStatistics.computeSnapshot(LoadStatistics.java:352)
at hudson.model.LoadStatistics$LoadStatisticsUpdater.doRun(LoadStatistics.java:394)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

I restart tomcat and my slave returns.... that is not very cool! But at least it came back Thanks again...

philbeiler@java.net (JIRA)

unread,
May 8, 2015, 7:21:03 AM5/8/15
to jenkinsc...@googlegroups.com
philbeiler edited a comment on Bug JENKINS-26582
Fortunately, I was able to easily duplicate the problem in about 5 minutes, first crack! Hopefully you can too!  !screenshot-1.png!


Ubuntu 15.04    - Does not matter, not what I'm running in prod
Jenkins  1.612  - Does not matter, not what I'm running in prod -- seems like this problem started around 1.597??? Not really sure when.

Install Git Plugin
Two slaves  s1 and s2  both on localhost  - each with 2 executors  s1 label S1, s2 label with S2  (I run no executors on master in prod, just an FYI)
Create a Matrix job
  GIT REPO  https://github.com/allegro/axion-release-plugin.git   (use this repo, as I'm using a hash for this repository - no auth required )
   Branches to build: origin/master
   Additional Behavoir -> Local Branch Name: master
Schedule:  H 0 1 1 0
Configuration  Matrix     Label Expression      label_exp   S1 S2

Build   Execute Shell   Command      echo "--------------->"$label_exp

Per the gentleman's comment above -- simply post this url in another browser tab and watch your threads die...  Keep submitting, and they all die...


http://localhost:8080/jenkins//git/notifyCommit?url=https%3A%2F%2Fgithub.com%2Fallegro%2Faxion-release-plugin.git&branches=master&sha1=a5de4d725814ff907a8cf1f5666b9f01e8361655

SEVERE: Unexpected executor death
java.lang.IllegalStateException: /usr/share/tomcat8/.jenkins/jobs/test/configurations/axis-label_exp/S1/builds/3 already existed; will not overwite with test/label_exp=S1 #3
at hudson.model.RunMap.put(RunMap.java:189)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284)
at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor$1.call(Executor.java:328)
at hudson.model.Executor$1.call(Executor.java:310)
at hudson.model.Queue._withLock(Queue.java:1251)
at hudson.model.Queue.withLock(Queue.java:1189)
at hudson.model.Executor.run(Executor.java:310)

Let me know if this does not work, or you want some config files. I hope it is easily reproducible..and quickly resolved -- this is killing me!  Thanks so much for your help...

This is even worse..  I lose my node after a while -- I saw this in  product  production  and but I did not think it was related...

!screenshot-2.png!

 No Now  I have these messages in the log... 
I restart tomcat and my slave returns....  that is not very cool!  But at least it came back !!
  Thanks again...

philbeiler@java.net (JIRA)

unread,
May 13, 2015, 1:22:02 PM5/13/15
to jenkinsc...@googlegroups.com

Was anyone able to replicate this problem? Just want to help out where I can, and am hoping for a quick resolution. Thanks.

jglick@cloudbees.com (JIRA)

unread,
May 13, 2015, 1:38:02 PM5/13/15
to jenkinsc...@googlegroups.com

I plan to try.

jglick@cloudbees.com (JIRA)

unread,
May 13, 2015, 1:58:02 PM5/13/15
to jenkinsc...@googlegroups.com
Jesse Glick started work on Bug JENKINS-26582
 
Change By: Jesse Glick
Status: Open In Progress

jglick@cloudbees.com (JIRA)

unread,
May 13, 2015, 2:02:01 PM5/13/15
to jenkinsc...@googlegroups.com

I get this ISE the second and subsequent time I trigger the build. The first time I get something different (with matrix-project 1.4.1):

java.io.IOException: cannot start a build of JENKINS-26582/label_exp=S1 since its parent has no builds at all
	at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:276)
	at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
	at hudson.model.Executor$1.call(Executor.java:328)
	at …

Will investigate both.

All the builds actually seem to run.

jglick@cloudbees.com (JIRA)

unread,
May 13, 2015, 2:10:01 PM5/13/15
to jenkinsc...@googlegroups.com

I filed the NPE as JENKINS-28384. It was probably triggered by the executor death here, but is an independent bug.

jglick@cloudbees.com (JIRA)

unread,
May 13, 2015, 3:57:01 PM5/13/15
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
 

Here is what I have so far. Despite appearances, this is not a core bug. A change made as part of the implementation of

JENKINS-24380 merely made an erroneous condition be displayed as such.

The critical point (and the reason why existing automated tests did not catch this) is that the bug is not manifested when you trigger a matrix build normally—only when you install the Git plugin and use /git/notifyCommit.

The main bug is in matrix-project: MatrixConfiguration.newBuild assumes without checking that the newly created MatrixRun in fact has a unique build number. If this was created as part of a MatrixBuild, then that will be true, since the MatrixProject uses the default (sane) implementation of newBuild. And that is exactly what happens—normally.

But it turns out that there is nothing blocking a MatrixRun from being created other ways. For example, if you ping <job>/label_exp=S1/build you will get this error, because the number of the last parent MatrixBuild is unchanged, and there was already a MatrixRun with that number. Of course you would not normally go to this URL—it is not exposed in the UI—but there is nothing stopping you from doing that, or I guess from using the CLI to do the same.

I presume the initial …since its parent has no builds at all exception has the same cause: an attempt to directly start a MatrixRun without a parent MatrixBuild.

Now the reason why this appears with Git notifications is that GitStatus.JenkinsAbstractProjectListener.onNotifyCommit is wrong, too. If you look at SubversionRepositoryStatus or MercurialStatus, you will see that they check whether there is an SCMTrigger for the project which does not ignorePostCommitHooks. If there is not, they print a message (No subversion jobs using SCM polling or all jobs using SCM polling are ignoring post-commit hooks, No SCMTrigger on …), and then do nothing. And if sha1 is unspecified, GitStatus does the same. But if you specify sha1, it immediately schedules a build (with RevisionParameterAction), rather than using polling, even if there is no SCMTrigger.

For a top-level project, that is probably fine. But MatrixConfiguration.getScm delegates to its parent, so each configuration shows up in the list of projects matching the specified repo. Thus means that the Git plugin schedules not only the top-level MatrixProject into the queue, but each MatrixConfiguration! And when those children are run directly, the error appears because they are trying to create builds which duplicate an existing number: either that of the last matrix build (if the configurations get scheduled before the parent), or that of the current matrix build (if after).
Change By: Jesse Glick
Component/s: git-plugin
Component/s: matrix-project-plugin
Component/s: core

jglick@cloudbees.com (JIRA)

unread,
May 13, 2015, 4:02:03 PM5/13/15
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
ISE from RunMap.put using /git/notifyCommit on a matrix project

Mark Sinclair sorry to hijack this issue but everyone else seems to be seeing a problem with matrix projects and Git notifications, whereas your case was actually something else, apparently rarer and probably needing some unrelated fix. If you still see it, file it separately (blocking

JENKINS-24380 ).
Change By: Jesse Glick
Summary: ISE from RunMap.put  after reloading config  using /git/notifyCommit on a matrix project

gentoo.integer@gmail.com (JIRA)

unread,
May 13, 2015, 6:19:02 PM5/13/15
to jenkinsc...@googlegroups.com
Kanstantsin Shautsou commented on Bug JENKINS-26582
 
Re: ISE from RunMap.put using /git/notifyCommit on a matrix project

Issue can be masked because not all plugins using onNotifyCommit in github-plugin migration is in progress and other plugins just copy-pasted from github-plugin algorithm/code.

scm_issue_link@java.net (JIRA)

unread,
May 13, 2015, 10:20:03 PM5/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Jesse Glick
Path:
src/main/java/hudson/plugins/git/GitStatus.java
http://jenkins-ci.org/commit/git-plugin/de3117def8625c57a95126a200e990ab0481948e
Log:
[FIXED JENKINS-26582] To trigger a build from notifyCommit, the project must have an SCMTrigger.
This is true even if it has a matching SCM and sha1 is specified.
Otherwise we would be triggering MatrixConfiguration, which is illegal and cause errors.

scm_issue_link@java.net (JIRA)

unread,
May 13, 2015, 10:20:04 PM5/13/15
to jenkinsc...@googlegroups.com
SCM/JIRA link daemon resolved as Fixed
 
Change By: SCM/JIRA link daemon
Status: In Progress Resolved
Resolution: Fixed

scm_issue_link@java.net (JIRA)

unread,
May 13, 2015, 10:20:05 PM5/13/15
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Mark Waite
Path:
src/main/java/hudson/plugins/git/GitStatus.java
src/test/java/hudson/plugins/git/GitSCMTest.java
http://jenkins-ci.org/commit/git-plugin/b88b388aee1085e5d161c578c3f551953b27abf4
Log:
Merge pull request #319 from jglick/SCMTrigger-

JENKINS-26582

JENKINS-26582 notifyCommit should ignore projects without SCMTrigger

Passed tests on multiple platforms.

Compare: https://github.com/jenkinsci/git-plugin/compare/6c1c49feefb3...b88b388aee10

philbeiler@java.net (JIRA)

unread,
May 18, 2015, 6:24:02 AM5/18/15
to jenkinsc...@googlegroups.com

I was having a hard time following the comments, it that it would actually fix the dead thread problem. Now that this fix was integrated into the head (according to emails that I recieved from the Jenkins server, I decided to retry the test, but I get the same results..

philbeiler@java.net (JIRA)

unread,
May 18, 2015, 6:24:04 AM5/18/15
to jenkinsc...@googlegroups.com
philbeiler updated an issue
Change By: philbeiler
Attachment: screenshot-3.png

philbeiler@java.net (JIRA)

unread,
May 18, 2015, 6:24:06 AM5/18/15
to jenkinsc...@googlegroups.com
philbeiler edited a comment on Bug JENKINS-26582
I was having a hard time following the comments, it that it would actually fix the dead thread problem. Now that this fix was integrated into the head (according to emails that I  recieved  received  from the Jenkins server, I decided to retry the test, but I get the same results..

philbeiler@java.net (JIRA)

unread,
May 18, 2015, 6:25:01 AM5/18/15
to jenkinsc...@googlegroups.com

philbeiler@java.net (JIRA)

unread,
May 18, 2015, 6:25:02 AM5/18/15
to jenkinsc...@googlegroups.com
philbeiler edited a comment on Bug JENKINS-26582
I was having a hard time following the comments,  it that it  if these changes  would actually fix the dead thread problem. Now that this fix was integrated into the head (according to emails that I received from the Jenkins server, I decided to retry the test, but I get the same results..

daniel@beckweb.net (JIRA)

unread,
May 18, 2015, 4:00:02 PM5/18/15
to jenkinsc...@googlegroups.com

philbeiler The fixes are in the Git Plugin and have not been released yet.

msinclair@juniper.net (JIRA)

unread,
May 18, 2015, 4:11:04 PM5/18/15
to jenkinsc...@googlegroups.com

I had originally reported this issue. For my application (freestyle jobs), I see the dead thread problem after a config reload. This resolution won't solve the problem for those that are seeing the problem after reloading configuration (I don't have the Git Plugin).

daniel@beckweb.net (JIRA)

unread,
May 18, 2015, 4:33:01 PM5/18/15
to jenkinsc...@googlegroups.com

Mark Sinclair Well, this is a mess then

Phil's explanation was so good and easily reproducible that Jesse went ahead and fixed it using this issue as reference. Notably, most commenters also used Matrix Projects and provided information and stack traces related to that, so it's understandable that the difference in the original report was missed.

The cleanest way to move forward would be to file your original issue a second time. Mention that it's not

JENKINS-26582 , as its resolution helps with Matrix projects and Git plugin, but your problem is with Freestyle projects, to protect it from being hijacked again. I understand this must be frustrating but using this issue going forward, when it was already used in the fixes to Git Plugin, would be too confusing IMO.

It would also be great if you could make your issue reliably reproducible in some way.

jglick@cloudbees.com (JIRA)

unread,
May 27, 2015, 2:10:02 PM5/27/15
to jenkinsc...@googlegroups.com

Mark Sinclair perhaps you missed my comment of May 13th where I said essentially the same thing, but perhaps not explained as well as Daniel.

jglick@cloudbees.com (JIRA)

unread,
May 27, 2015, 2:11:04 PM5/27/15
to jenkinsc...@googlegroups.com

Please note that there are fixes for this issue in both the Git and Matrix Project plugins. I believe either suffices to avoid the symptom. Not sure about release status, check plugin changelogs.

msinclair@juniper.net (JIRA)

unread,
May 27, 2015, 2:18:01 PM5/27/15
to jenkinsc...@googlegroups.com

Thanks - hadn't noticed that. I will get the latest and give it a try when it's released.

philbeiler@java.net (JIRA)

unread,
May 28, 2015, 8:13:04 AM5/28/15
to jenkinsc...@googlegroups.com

I apologize for for hijacking this issue.. That was not my attempt, as the symptoms/issue produced the same outcome – it just seemed like the right place to jump in!

I hope I can ask one last question on this, Jesse stated that both the Git and Matrix plugin have been fixed. The matrix plugin has not been released in almost a year, and the Git plugin was last released in February. Is there any plan for releasing them (I'm sure they are not your responsibility), but this but is killing me (or my threads!) Is there some way that I can monitor these fixes (related ticket numbers, etc), as they go thru the automated process, similar to the core Jenkins code? I would just like to know how long I have to deal with this, especially, since you were so kind to fix it weeks ago.
Thanks again. Phil

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 6, 2015, 9:13:03 AM6/6/15
to jenkinsc...@googlegroups.com

philbeiler the git plugin and git client plugin are being tested in hopes of releasing new versions before the end of June. If you're willing to assist with the testing, please download and install a pre-release build of the git client plugin and the git plugin. Problems detected in the pre-release should be e-mailed to Mark Waite and Nicolas De Loof.

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 6, 2015, 9:22:02 AM6/6/15
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-26582
[~philbeiler] the git plugin and git client plugin are being tested in hopes of releasing new versions before the end of June. If you're willing to assist with the testing, please download and install a pre-release build of the [git client plugin|https://drive.google.com/file/d/0B9GyYWyfT1N5Y3p5TVlMNFRFWVk/view?usp=sharing] and the [git plugin|https://drive.google.com/file/d/0B9GyYWyfT1N5d2VRUW1BRDB5SkU/view?usp=sharing]. Problems detected in the pre-release should be e-mailed to [~MarkEWaite] and [~ndeloof].

I wrote some [test ideas|https://docs.google.com/document/d/1e7AEuSPCmPynkfAuFBLMRS4rVVg8-02M_p4BVRk2g5Y/edit?usp=sharing] if you would like suggestions of areas that need testing.  The git plugin supports many different use cases and its automated tests only evaluate a very few of those use cases.

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 6, 2015, 5:34:02 PM6/6/15
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-26582
[~philbeiler] the git plugin and git client plugin are being tested in hopes of releasing new versions before the end of June. If you're willing to assist with the testing, please download and install a pre-release build of the [git client plugin|https://drive.google.com/file/d/0B9GyYWyfT1N5Y3p5TVlMNFRFWVk/view?usp=sharing] and the [git plugin|https://drive.google.com/file/d/0B9GyYWyfT1N5d2VRUW1BRDB5SkU/view?usp=sharing]. Problems detected in the pre-release should be e-mailed to [~MarkEWaite] and [~ndeloof].

I wrote some [test ideas|https://docs.google.com/document/d/1e7AEuSPCmPynkfAuFBLMRS4rVVg8-02M_p4BVRk2g5Y/edit?usp=sharing] if you would like suggestions of areas that need testing.  The git plugin supports many different use cases and its automated tests only evaluate a very few of those use cases.


I ran through the steps described in this bug report with a matrix job running across slaves on multiple versions of Windows and multiple versions of Linux (CentOS, Debian, and Ubuntu).  As far as I can tell, the bug is fixed by the changes made by [~jglick].

jglick@cloudbees.com (JIRA)

unread,
Jun 8, 2015, 6:53:01 PM6/8/15
to jenkinsc...@googlegroups.com

I have released Matrix Project 1.5 with this fix.

prosegay@voltdb.com (JIRA)

unread,
Sep 17, 2015, 10:21:03 AM9/17/15
to jenkinsc...@googlegroups.com
philip rosegay reopened an issue
 

I've got 1.609.3 LTS installed with git plugin 2.4.0 and matrix project 1.6 and I'm getting lots of

java.lang.IllegalStateException: /var/lib/jenkins/jobs/java8-1-build-pro-java7-master/builds/1388 already existed; will not overwite with java8-1-build-pro-java7-master #1388
at hudson.model.RunMap.put(RunMap.java:187)
at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178)
at hudson.model.AbstractProject.newBuild(AbstractProject.java:1010)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1209)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor$1.call(Executor.java:335)
at hudson.model.Executor$1.call(Executor.java:317)
at hudson.model.Queue._withLock(Queue.java:1348)
at hudson.model.Queue.withLock(Queue.java:1213)
at hudson.model.Executor.run(Executor.java:317)

I recently started using github push triggers (manually configured). this ticket tldr. Did i miss something (sorry)? I'm limping along with this. Thanks.
Change By: philip rosegay
Resolution: Fixed
Status: Closed Reopened

jglick@cloudbees.com (JIRA)

unread,
Sep 17, 2015, 1:26:04 PM9/17/15
to jenkinsc...@googlegroups.com
Jesse Glick resolved as Fixed
 

philip rosegay if you have applied the relevant plugin updates then you are hitting a different bug with the same symptom but a distinct cause, which would be tracked separately. Without knowing how to reproduce we are unlikely to be able to help.
Change By: Jesse Glick
Status: Reopened Resolved
Resolution: Fixed

prosegay@voltdb.com (JIRA)

unread,
Sep 17, 2015, 1:43:02 PM9/17/15
to jenkinsc...@googlegroups.com
philip rosegay commented on Bug JENKINS-26582
 
Re: ISE from RunMap.put using /git/notifyCommit on a matrix project

ya think? the stack trace looked the same to me. what do you need?

prosegay@voltdb.com (JIRA)

unread,
Sep 17, 2015, 1:44:02 PM9/17/15
to jenkinsc...@googlegroups.com
philip rosegay edited a comment on Bug JENKINS-26582
ya think?  seems unlikely as  the stack trace looked the same to me. what do you need?

jglick@cloudbees.com (JIRA)

unread,
Sep 17, 2015, 1:48:04 PM9/17/15
to jenkinsc...@googlegroups.com

Jenkins core is simply reporting an illegal condition which something else was responsible for producing. Other than the original report here, all cases have been tracked back to a combination of bugs in the Git and Matrix Project plugins, both of which were fixed. What is causing the problem in your case I do not know.

prosegay@voltdb.com (JIRA)

unread,
Sep 18, 2015, 6:31:02 AM9/18/15
to jenkinsc...@googlegroups.com

didn't answer the question: what do you need to isolate to root cause?

mark.earl.waite@gmail.com (JIRA)

unread,
Sep 18, 2015, 7:31:02 AM9/18/15
to jenkinsc...@googlegroups.com

Usually, isolating a problem to root cause needs enough description of the distinct conditions which caused the problem so that someone else can duplicate the problem.

In this case, it may need a support bundle (to show the versions of various plugins installed), a copy of the job definition (or a detailed enough description of the job definition that someone can recreate the job from that description), and a description of the actions taken to show the problem.

jglick@cloudbees.com (JIRA)

unread,
Sep 18, 2015, 10:42:03 AM9/18/15
to jenkinsc...@googlegroups.com

Right, ideally a way to reproduce the problem from scratch. When that cannot be found, there may be some clues that are helpful (for example: only happens when a certain plugin is installed/configured), but in general the problem may not be fixable. For certain bugs of course the error message/stack trace suffices to guess at a diagnosis. Unfortunately that is not the case here.

david.harris@garnercorp.com (JIRA)

unread,
Dec 11, 2015, 12:59:01 PM12/11/15
to jenkinsc...@googlegroups.com

Is this the best/current bug to discuss the 'dead node' issue? Should I be using JENKINS-29268 or something else instead?

This bug is affecting us pretty badly (team of ~15 developers) and we're willing to put some work in to help get it fixed.

Thanks in advance

mark.earl.waite@gmail.com (JIRA)

unread,
Dec 11, 2015, 6:09:02 PM12/11/15
to jenkinsc...@googlegroups.com

I don't think a resolved issue is generally a good place to discuss an issue you're currently seeing. If there is an open issue that is the same, or appears strongly related, that would be a reasonable place for the discussion.

If the issue is still there, and this describes that issue, then I think this bug should be reopened.

jglick@cloudbees.com (JIRA)

unread,
Jan 11, 2016, 6:25:03 PM1/11/16
to jenkinsc...@googlegroups.com

Do not reopen this issue.

There is a known but unconfirmed occurrence when using reload-from-disk. If you know of some other means of reproducing, mention in JENKINS-27530.

mark.earl.waite@gmail.com (JIRA)

unread,
Oct 22, 2019, 9:33:22 PM10/22/19
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Fixed
 
Change By: Mark Waite
Status: Resolved Closed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages