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

Matrix parent build shouldn't consume an executor.

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hi,

      On a multi-configuration project, I encounter a systematic deadlock because the
      parent job and one of its child are queued on the same node.

      The configuration matrix is as follows:
      [x] Build on multiple nodes
      [-] Individual nodes
      [x] APOLLON (apollon)
      [x] CHRONOS (chronos)
      [x] DEMETER (demeter)
      [ ] EOS (eos)
      [x] EROS (eros)
      [x] PAN (pan)
      [x] PONTOS (pontos)
      [ ] master (the master Hudson node)
      [+] Labels
      [ ] Axes

      Here is the console output:

      started
      Building remotely on PONTOS
      Triggering label=PAN
      Triggering label=APOLLON
      Triggering label=DEMETER
      Triggering label=PONTOS
      Triggering label=EROS
      Triggering label=CHRONOS

      All jobs except the ones on "PONTOS" successfully terminate.
      The parent job keeps executing, waiting for all its children termination, but it
      never stops as the child job supposed to run on "PONTOS" remains in the build queue.

      Enabling the master Hudson node has no effect. Its corresponding job also
      remains in the build queue.

      Thank you for reading.

      Regards,
      Regis.

        Attachments

          Issue Links

            Activity

            Hide
            kohsuke Kohsuke Kawaguchi added a comment -

            The original issue, which is that the matrix parent build consumes an executor, is fixed indeed in 1.337. In the executor table, the parent build will show up without an executor number — think of it as getting executed in a temporary executor.

            People then started talking about other related but different issues, such as the fact that the matrix parent execution cannot be tied to a specific node.

            Since this issue is getting overloaded with multiple things, I'm closing this bug once and for all.

            If you think you hit a bug, please open a new one.

            Thanks!

            Show
            kohsuke Kohsuke Kawaguchi added a comment - The original issue, which is that the matrix parent build consumes an executor, is fixed indeed in 1.337. In the executor table, the parent build will show up without an executor number — think of it as getting executed in a temporary executor. People then started talking about other related but different issues, such as the fact that the matrix parent execution cannot be tied to a specific node. Since this issue is getting overloaded with multiple things, I'm closing this bug once and for all. If you think you hit a bug, please open a new one . Thanks!
            Hide
            rdesgroppes Régis Desgroppes added a comment -

            I agree with Kohsuke: closed.

            Show
            rdesgroppes Régis Desgroppes added a comment - I agree with Kohsuke: closed.
            Hide
            imakowski Ireneusz Makowski added a comment -

            I still have this issue on latest LTS. It blocks our executors when Restrict label for matrix job is used!

            Show
            imakowski Ireneusz Makowski added a comment - I still have this issue on latest LTS. It blocks our executors when Restrict label for matrix job is used!
            Hide
            imakowski Ireneusz Makowski added a comment -

            See my latest comment

            Show
            imakowski Ireneusz Makowski added a comment - See my latest comment
            Hide
            danielbeck Daniel Beck added a comment -

            It blocks our executors when Restrict label for matrix job is used!

            Please file a new issue, and include specific information on how to reproduce this.

            https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue

            Show
            danielbeck Daniel Beck added a comment - It blocks our executors when Restrict label for matrix job is used! Please file a new issue, and include specific information on how to reproduce this. https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue

              People

              • Assignee:
                rdesgroppes Régis Desgroppes
                Reporter:
                rdesgroppes Régis Desgroppes
              • Votes:
                24 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: