|
||||||||
|
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.
@Kohsuke, Do we have a rough idea on which LTS release would have this fix. We are using LTS 1.532 on CentOS for our CI which is expected to be online 24x7x365, and we see this issue that seems to pop up on around 30 of our slaves every week or so.
@Oleg, we would not want the workaround mentioned since all our slaves are not expected to have any overhead whatsoever due to any other running process.