|
||||||||
|
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/groups/opt_out.
Is there any update to this issue? All I can tell from the stacktrace is that at the end of the build, Jenkins requests that the slave kill the remaining processes. But, before it can do so it receives a response that the Connection was terminated due to some failure during a read operation(can't see the reason behind the failure in the stacktrace). Doesn't this seem like some kind of race condition where the slave is trying to finish up and kill the remaining processes while the master terminates the connection before the slave can finish?