CI Reliability 2026-05-21
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Failures in node-test-pull-request/73490 to node-test-pull-request/73588 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-21.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-21 00:35 | 1 | 27 | 13 | 7 | 52 | 29.35% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-21.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(3) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(4) -
sh: line 12: [: -gt: unary operator expected(9) -
ERROR: out of memory(4) -
fatal: No rebase in progress?(4) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(3) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(2) -
sequential/test-watch-mode-worker(5) -
parallel/test-worker-nearheaplimit-deadlock(2) -
sequential/test-watch-mode-restart-esm-loading-error(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
test-runner/test-run-watch-repeatedly(2) -
test-runner/test-run-watch-run-duration(2) -
wpt/test-hr-time(2)
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 with reports/2026-05-21.md and the generated ncu-ci walk pr --stats=true --markdown report for the detailed failure context. Review the listed timeout, repository-fetch, shell, resource, build, and test failures, then use the linked CI runs to investigate them. Done means the recurring failures in the Progress list are addressed and CI reliability improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100