|
||||||||
|
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.
I apologize, Daniel. I just realized the Jenkins-related JIRA emails were going into a spam folder. Hence my radio silence. As far as I can tell, the issues that prompted this ticket were caused by some underlying network issues that were the result of a poorly configured firewall sitting between our build machine various other machines accessed during our builds. TCP connections were getting borked at the packet level, and apparently the networking code (somewhere, possibly not in Jenkins) doesn't handle the case when a low level socket operation blocks indefinitely.