|
||||||||
|
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.
We have constructed a simple test case that brings out the bug. It is 100% reproducible.
1) Configure a cloud that can run Jenkins slaves. Use just 1 executor.
2) Configure a job that puts a JUnit file in the workspace. We simply download junit files from a web server.
3) Add an xUnit processing step for the file.
4) Make the job build itself after it finishes.
With this setup, we have noticed that the freeze up happens on the 20th build on the slave, regardless of the number of the jobs. For example, with a two job config we managed to build 10+9 succesfully, with the slave being stuck on the 20th build.ยด
We've reproduced this with RHEL 5, RHEL6 and Ubuntu 12.01.