[JIRA] (JENKINS-15957) All build executors permanently "Dead!"

[tortoise...@yahoo.co.uk (JIRA)]

Bruce Adams commented on JENKINS-15957 All build executors permanently "Dead!" After being left overnight all the threads are dead again with a very similar assertion. java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #7028 EXACT: lo=6,hi=1,size=7,size2=7 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:418) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:502) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:355) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:100) at hudson.model.Job.getLastBuildsOverThreshold(Job.java:856) at hudson.model.Job.getEstimatedDuration(Job.java:863) at hudson.model.queue.MappingWorksheet.<init>(MappingWorksheet.java:320) at hudson.model.queue.MappingWorksheet.<init>(MappingWorksheet.java:303) at hudson.model.Queue.maintain(Queue.java:1033) at hudson.model.Queue.pop(Queue.java:861) at hudson.model.Executor.grabJob(Executor.java:284) at hudson.model.Executor.run(Executor.java:205) I wondered if #7028 referred to a build number but I have builds 7025, 7025 and 7029 only in the 7000 series. As a workaround to JENKINS-14583 I set each job to start with a different build number 1000 apart. However after restarting all the builds think the last build was the last one in 10000 series even though there are on different nodes.

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