|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I don't have a specific way to reproduce. Here are some conditions that were true both times the failure occured:
-Multiple slaves all busy and about 50 jobs in the build queue. Some jobs have been sitting in the build queue for 12+ hours.
-Implement configuration changes across many jobs by editing the config.xml files directly in linux/emacs. config.xml is the only file touched.
-reload configuration via <jenkins-url>/reload from my browser. Jenkins asks me to 'POST' the command, which I hit the "tryPOSTing" button and then it reloads.
After the reload, when an executor becomes free, it picks up a job from the queue and immediately fails with the dead indicator in the executor status sidebar. When the thread is restarted, it picks up another job from the queue and dies again. The process repeats until the queue is empty.
It is unclear if jobs that were not in the queue at the time of reload would die. I'm not sure if after the reload all jobs need to die one time or just the jobs that were in the queue at the time of the reload.
It is true that the problem is self correcting, after a job dies one time, the build number gets corrected and it will run properly the next time.
This doesn't happen every time I reload config.