[JIRA] [master-slave] (JENKINS-5413) SCM polling getting hung

Wed, 09 Jul 2014 18:43:33 -0700

Thanks. Adding that line does fix the execution error. However, the full script, while it also reports successful-looking output, fails to interrupt any threads.

[EnvInject] - Loading node environment variables.
Building in workspace /Users/sbuxagent/Jenkins/Home/jobs/Zap Polling Threads/workspace
android-malaysia
1 day 16 hr
1404809940627
Interrupting thread SCM polling for hudson.matrix.MatrixProject@2e2cb699[android-malaysia]
ios-hongkong
1 day 16 hr
1404810120578
Interrupting thread SCM polling for hudson.matrix.MatrixProject@128e42d[ios-hongkong]
ios-china
1 day 16 hr
1404809940628
Interrupting thread SCM polling for hudson.matrix.MatrixProject@68f60dc8[ios-china]
Script returned: [hudson.triggers.SCMTrigger$Runner@2e2cb699, hudson.triggers.SCMTrigger$Runner@128e42d, hudson.triggers.SCMTrigger$Runner@68f60dc8]
Finished: SUCCESS


I can run the script over and over, and it continues to report those same three thread IDs.



I don't know why, but this stuck-thread problem disappeared for a couple of weeks. Now it's back. I'm going to update to the latest jenkins from 1.565 and see if anything's improved.
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.

Reply via email to