commit-queue times out after 15 mins while it usually takes <3 mins

[trivikr]

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
...

Details: https://github.com/nodejs/node/actions/runs/30765170760/job/91542478131

First timeout

...
+ MULTIPLE_COMMIT_POLICY=--oneCommitMax
+ git node land --autorebase --yes --oneCommitMax 64772
Error: The operation was canceled.

Details: https://github.com/nodejs/node/actions/runs/30783328197/job/91592125884

[trivikr]

The retry attempt took close to 15 mins, but was successful
https://github.com/nodejs/node/actions/runs/30783328197/job/91601263185

[trivikr]

This can be closed if issue doesn't persist.

[Renegade334]

This happens to GHA jobs on the slim runners from time to time.

[aduh95]

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-queue Add this label to land a pull request using GitHub Actions. 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 🫣