ubuntu-slim runners time out after 15 mins while it usually takes <3 mins
Open
Nobody has claimed this yet.
meta
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
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
...
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the linked successful and timed-out GitHub Actions jobs, focusing on the git node land --autorebase --yes --oneCommitMax step on the ubuntu-slim runner. Reproduce or trace why the operation is canceled after 15 minutes; done means the command completes within its usual runtime on ubuntu-slim.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript, ubuntu
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100