|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
It seems we are having a similar problem. All of our executors were dead today with the following stacktrace:
java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #12608 DESC: lo=97,hi=95,size=98,size2=98
at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:418)
at hudson.model.AbstractProject.getNearestOldBuild(AbstractProject.java:1025)
at hudson.maven.MavenModuleSetBuild.getModuleLastBuilds(MavenModuleSetBuild.java:434)
at hudson.maven.MavenModuleSetBuild.getResult(MavenModuleSetBuild.java:189)
at hudson.model.Job.getLastBuildsOverThreshold(Job.java:853)
at hudson.model.Job.getEstimatedDuration(Job.java:864)
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)
This weekend, the daylight saving just ended and the clocks went back one hour, so it seems the same problem Alexander described.
Besides removing the builds, are there other workarounds?