Re: [PR] ci: name the Ubuntu image instead of asking for the queue [maka]

["Astro-Han (via GitHub)" <gi...@apache.org>]

Astro-Han commented on PR #4483:
URL: https://github.com/apache/maka/pull/4483#issuecomment-5496375993

   This PR's own checks turned into the controlled experiment the description said the run history could not provide. Same push, same `created_at` to the second, label the only variable.
   
   **Its first push (15:11:42Z), when only `dependency-audit` was pinned:**
   
   | queue | label | job |
   |---|---|---|
   | **9.2 min** | `ubuntu-latest` | CI / test |
   | **8.8 min** | `ubuntu-latest` | PR effort label / label |
   | **3 s** | `ubuntu-24.04` | Dependency audit / audit |
   
   **#4482's push at 15:10:33Z, eight jobs created in the same second:**
   
   | queue | label | job |
   |---|---|---|
   | **7.7 min** | `ubuntu-latest` | Gitoxide helper admission / ubuntu-latest |
   | **7.7 min** | `ubuntu-latest` | PR effort label / label |
   | 24 s | `windows-latest` | Gitoxide helper admission / windows-latest |
   | 23 s | `macos-latest` | Gitoxide helper admission / macos-latest |
   | 6 s | `ubuntu-24.04-arm` | CLI package validation / linux-arm64 |
   | 4 s | `macos-15` | CLI package validation / darwin-arm64 |
   | 3 s | `windows-2025` | CLI package validation / win32-x64 |
   | **3 s** | `ubuntu-24.04` | CLI package validation / linux-x64 |
   
   That is the same-instant `ubuntu-latest` vs `ubuntu-24.04` comparison the description listed as missing: **7.7 minutes against 3 seconds, from one push.**
   
   **After the full pin (15:26:15Z):** CI / test on `ubuntu-24.04` waited 3.3 min. So did `windows-latest` (3.2), `macos-15` (1.8) and the other pinned Linux jobs — a brief global wobble in that window, not something specific to a label. `windows-2025` and `ubuntu-24.04-arm` in the same batch took 20 and 19 seconds.
   
   **And the direct comparison:** #4482's CI / test, created 15:21:39Z on `ubuntu-latest`, was still queued nine minutes later. This PR's CI / test, created 15:26:15Z on `ubuntu-24.04` — **four and a half minutes later** — started at 15:29:35Z and was already running by then.
   
   This does not explain the mechanism. The likeliest reading is still that ASF-wide demand saturates whatever capacity is behind the `ubuntu-latest` name during working hours while the pinned name is not contended, and nothing here proves that. What it does settle is the part the description flagged as unproven: asking for `ubuntu-24.04` instead of `ubuntu-latest`, from the same push at the same second, gets a runner in seconds instead of minutes.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org