[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs

Fri, 23 Nov 2012 05:23:51 -0800

 
Alexander Schmacks edited a comment on Bug JENKINS-15652

I'm not sure that this problem is directly related to a recent Jenkins update.
In our environment (Jenkins 1.489 on Windows 2003 server) this exception started to appear last Friday. An update to Jenkins 1.491 didn't help. Neither did a downgrade back to 1.489.

But after thinking about it: we had troubles with our time server last Friday so that suddenly the server clock changed from Friday noon to Thursday evening.
This lead to some "past" builds referencing previous builds from the "future" - at least this is what Jenkins seems to see now.

I've noted the problematic build numbers in the log and searched in the build.xml files in our jobs directory. Some single build directories had the wrong timestamp in their name (in the past) - which I corrected to a date that's more appropriate (not knowing the real build timestamp anymore I had to make an educated guess ).
I.e., it seems that Jenkins builds the job history by the directory names.

Once these timestamped directory names were corrected the exception didn't appear again, the executor's not dying anymore.
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