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

Pairs of throttled node labels no longer seem to work starting from version 1.536

    XMLWordPrintable

Details

    Description

      我们使用此功能只允许使用 cuda 设备的有限数量的作业（请参阅配置截图）。从 1.536 版开始，这似乎不再起作用，因为在标签为“gpu”的节点上执行了多个具有“CUDA”类别的作业。

      Attachments

        1. Global.png
          Global.png
          9 kB
        2. Job.png
          Job.png
          5 kB

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-27708 Concurrent build limits not honored on Jenkins 1.607

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-19986 Throttle Concurrent Builds plugin doesn't appear to work

          • Major - Major loss of function.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            View 9 older comments
            danielbeck Daniel Beck added a comment -

            Possibly related to the queue concurrency issue introduced in 1.536 or so. Apparently it's easiest to see when you only have one CPU core, no hyperthreading. That was resolved in 1.607, with further fixes in 1.610 (no changelog entry for that yet).

            danielbeck Daniel Beck added a comment - Possibly related to the queue concurrency issue introduced in 1.536 or so. Apparently it's easiest to see when you only have one CPU core, no hyperthreading. That was resolved in 1.607, with further fixes in 1.610 (no changelog entry for that yet).
            dpcsar Dwane Pottratz added a comment -

            Looks to be working in 1.610

            dpcsar Dwane Pottratz added a comment - Looks to be working in 1.610
            danielbeck Daniel Beck added a comment -

            Anyone still experiencing this issue on 1.610+?

            danielbeck Daniel Beck added a comment - Anyone still experiencing this issue on 1.610+?
            triesz Peter Triesz added a comment -

            with 1.610 throttling started to work again for us. YEY. thanks a bunch.

            triesz Peter Triesz added a comment - with 1.610 throttling started to work again for us. YEY. thanks a bunch.
            danielbeck Daniel Beck added a comment -

            Assuming to be a duplicate of one of the recent queue processing fixes.

            danielbeck Daniel Beck added a comment - Assuming to be a duplicate of one of the recent queue processing fixes.

            People

              abayer Andrew Bayer
              simabeis Marcel Beister
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: