I'm also having a similar issue which is really blocking progress on out CI setup. I'm using Windows Server 2008 R2 with Jenkins running as a service. The problems appeared to start when I upgraded to 1.488 and created new jobs to use the 'View map from file' feature of the Perforce plugin. I subsequently upgraded to 1.489 but have now rolled back to 1.488.

Any suggestions/workarounds would be appreciated because our CI work is currently at a halt because of this.

Roger

Nov 9, 2012 9:10:27 AM hudson.triggers.SafeTimerTask run
SEVERE: Timer task hudson.model.Queue$MaintainTask@1de2b1 failed
java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #256 DESC: lo=11,hi=10,size=11,size2=11
at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:418)
at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207)
at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:100)
at hudson.model.Job.getLastBuildsOverThreshold(Job.java:813)
at hudson.model.Job.getEstimatedDuration(Job.java:820)
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$MaintainTask.doRun(Queue.java:1759)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)

Nov 9, 2012 9:10:27 AM jenkins.model.lazy.AbstractLazyLoadRunMap search
WARNING: Assertion error: failing to load #256 DESC: lo=11,hi=10,size=11,size2=11
java.lang.Exception
at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:417)
at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207)
at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:100)
at hudson.model.Job.getLastBuildsOverThreshold(Job.java:813)
at hudson.model.Job.getEstimatedDuration(Job.java:820)

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

Reply via email to