|
||||||||
|
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.
Hi I came across this problem today. I suspect it might be linked to restarting jenkins from curl. I suspect it may have not properly stopped the slave and that after the restart there may be two concurrent instances of the same slave in competition, causing from time to time a switch from one to one, but I have still to confirm that.