|
||||||||
|
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 have seen this issue as well. I just upgraded from 1.522 to 1.608. We're using an old Throttle plugin, 1.7.2, but it appears from the previous comments that this won't fix it.
I was able to figure out that the problem occurs when 2 jobs that are supposed to throttle under the same category are started at exactly the same time. I created a job that started two jobs when completed. All three run with the same throttle category on the same node. The two child jobs will be started simultaneously when one should block the other.
Hope this helps.