[JIRA] [matrix-project-plugin] (JENKINS-10944) Jobs "deadlocking" on remote slave

Wed, 19 Nov 2014 17:51:58 -0800

Tim Wood commented on Bug JENKINS-10944

Very much needing a solution for this issue. It basically makes matrix jobs worthless, because they may deadlock.

I've made two observations:

  • This occurs in the absence of the Throttle Concurrent Builds plugin.
  • It does not seem to occur in cases where all elements of the matrix do not start at the same time. That is, if the executors on a node the matrix job may run on are currently busy, that node's build of the matrix job gets queued, and the flyweight master task of the matrix build runs along with that node's build.
  • In cases where an executor is available on each node the matrix job may run on, occasionally all builds of the matrix job will get scheduled properly, including the one that runs concurrently with the flyweight master task. But usually, the deadlock happens. So there's some race between threads here, not just a straight-line logical error.
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