|
||||||||
|
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/d/optout.

I just noticed that the slave in question had not gotten the latest slave jar update (it was still running 2.13, where as the slave jar that comes with 1.565.1 is 2.43). I just updated the jar and restarted the slave service, and the problem seems to have cleared up. All three jobs in question just ran fine a couple times each. This might be worth checking for anyone else seeing this issue.