Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-23902

Matrix parent takes executor slot and blocks children

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Not sure when the behaviour changed, but the parent job used to take an extra "free" slot. Now it's taking an actual slot, which can end up being the only slot that one of its children can use, leading to an effective deadlock.

        Attachments

          Issue Links

            Activity

            Hide
            jameshowe James Howe added a comment -

            Upgrading to throttle-concurrents-1.8.4 did fix it.

            However, something has broken it again.
            Now on Jenkins 1.590, throttle-concurrents-1.8.4, matrix-project-1.4, priority-sorter-2.9.
            I thought it was a 1.590->1.593 update, but downgrading didn't resolve it.

            Show
            jameshowe James Howe added a comment - Upgrading to throttle-concurrents-1.8.4 did fix it. However, something has broken it again. Now on Jenkins 1.590, throttle-concurrents-1.8.4, matrix-project-1.4, priority-sorter-2.9. I thought it was a 1.590->1.593 update, but downgrading didn't resolve it.
            Hide
            jameshowe James Howe added a comment -

            Priority sorter is not in advanced mode.

            Show
            jameshowe James Howe added a comment - Priority sorter is not in advanced mode.
            Hide
            jameshowe James Howe added a comment -

            Odd. With no apparent changes to config or plugins, they started using flyweight executors again.

            Show
            jameshowe James Howe added a comment - Odd. With no apparent changes to config or plugins, they started using flyweight executors again.
            Hide
            simonrichter Simon Richter added a comment -

            I saw that happen when the slave node the job should have run on was down at that time and the matrix job was queued.

            Show
            simonrichter Simon Richter added a comment - I saw that happen when the slave node the job should have run on was down at that time and the matrix job was queued.
            Hide
            danielbeck Daniel Beck added a comment -

            There have been fixes to the queue behavior until 1.610. That version or higher would be needed for any follow-up issue to make sense.

            Show
            danielbeck Daniel Beck added a comment - There have been fixes to the queue behavior until 1.610. That version or higher would be needed for any follow-up issue to make sense.

              People

              Assignee:
              kohsuke Kohsuke Kawaguchi
              Reporter:
              jameshowe James Howe
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: