Last year we started using Jenkins and found an issue with Windows slaves deadlocking when running the Master on Linux. We analyzed the issue and implemented a patch in order for us to use Jenkins. I sent a pull request https://github.com/jenkinsci/jenkins/pull/665 that closes the connection when it notices a deadlock and thus preventing the builds from deadlocking. In the comment there is a link to the source to a plugin I use to reproduce the issue if anyone wants to help digging.
I think the problem is related to one build launching several windows programs that produces a lot of output. In the test program Jenkins will launch a build that executes around 100 instances of dir and ping. Now we upgraded to the latest LTS 1.509.1 and found that we needed to implement the same pach in order to prevent the builds from hanging. Could anyone verify the patch, we've been using it for about 4-5 months and we've tested it with 1.480.1 and 1.509.1. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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/groups/opt_out.
