Repository navigation
ubuntu-slim runners time out after 15 mins while it usually takes <3 mins #64972
Description
Last successful run which landed a PR
git node land was successful
...
+ MULTIPLE_COMMIT_POLICY=--oneCommitMax
+ git node land --autorebase --yes --oneCommitMax 63949
+ cat output
- Loading data for nodejs/node/pull/63949
...
First timeout
...
+ MULTIPLE_COMMIT_POLICY=--oneCommitMax
+ git node land --autorebase --yes --oneCommitMax 64772
Error: The operation was canceled.
Activity
trivikr commentedon Aug 3, 2026
The retry attempt took close to 15 mins, but was successful
https://github.com/nodejs/node/actions/runs/30783328197/job/91601263185
trivikr commentedon Aug 3, 2026
This can be closed if issue doesn't persist.
Renegade334 commentedon Aug 3, 2026
This happens to GHA jobs on the slim runners from time to time.
aduh95 commentedon Aug 4, 2026
There's clearly been an influx of those, I suspect a change on GH side. The issue is that the CQ can time out after removing the commit-queuePRs queued for automated landing through the Commit Queue.
label, but before being able to actually merge, so the PR is effectively kicked out of the CQ without notifying anyone. We could add another GHA job to try clean up, but if the problem is GHA reliability, it might be hopeless to try to solve it with GHA 🫣
tools: lazy-abort failed PR merges in CQ
panva commentedon Aug 7, 2026
This also happens to linters.yml, format-cpp, lint-cpp, and lint-js-and-md i've re-ran more than enough over the span of the last 2 weeks
[-]commit-queue times out after 15 mins while it usually takes <3 mins[/-][+]ubuntu-slim runners time out after 15 mins while it usually takes <3 mins[/+]aduh95 commentedon Aug 8, 2026
I wonder if it's a memory issue, in which case maybe adding some ESLint cache might help for
lint-js-and-md. Switching back toubuntu-latestis also an option, but a costly one (we prepare security releases from a private fork, where we have to pay for GHA usage)tools: delay removal of `commit-queue` label
tools: lazy-abort failed PR merges in CQ
tools: delay removal of `commit-queue` label
tools: lazy-abort failed PR merges in CQ
tools: delay removal of `commit-queue` label
tools: lazy-abort failed PR merges in CQ
30 remaining items
tools: avoid repeated subtree scans in must-call-assert
inoway46 commentedon Oct 24, 2026
I've reopened #66409 with updated benchmarks, including a two-CPU ARM approximation to assess private-repository costs. The results and cost estimates are in the PR description. Feedback on the runtime/cost trade-off would be welcome.
tools: add cache to `lint-js-and-md`
tools: avoid repeated subtree scans in must-call-assert
tools: use ubuntu-latest for public lint-js-and-md jobs
MikeMcC399 commentedon Nov 7, 2026
@inoway46
Thanks for continuing to work on this issue until it was resolved 👍🏻 (in #66409).
If there are other workflows that cause regular timeout issues on
ubuntu-slim, the same solution could be applied, so thatubuntu-latestis used, except dropping back toubuntu-slimin the private repo used for preparing security releases.tools: use ubuntu-latest for public CI jobs
tools: add cache to `lint-js-and-md`
tools: avoid repeated subtree scans in must-call-assert
tools: use ubuntu-latest for public lint-js-and-md jobs
tools: limit checkout for lint-addon-docs
tools: use ubuntu-latest for public lint-js-and-md jobs
tools: use ubuntu-latest for public lint-js-and-md jobs