CI Reliability 2026-08-12
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/75690 to node-test-pull-request/75784 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-08-12 00:17 | 2 | 25 | 17 | 7 | 49 | 27.47% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-08-12.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(3) -
ERROR: Error fetching remote repo 'origin'(4) -
Failed to trigger fanned build(2) -
Failed to trigger node-test-commit(2) -
fatal error: error in backend: IO failure on output stream: no space on device(2) -
fatal: No rebase in progress?(2) -
parallel/test-stream-pipeline-http2(13) -
parallel/test-esm-loader-hooks-inspect-wait(6) -
parallel/test-sqlite-backup(5) -
parallel/test-worker-terminate-http2-respond-with-file(5) -
test-runner/test-run-watch-cwd-isolation-none-argv(5) -
sequential/test-performance-eventloopdelay(4) -
sequential/test-watch-mode-restart-esm-loading-error(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(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-08-12.md and the generated ncu-ci walk pr --stats=true --markdown reports/2026-08-12.md output. Inspect the linked node-test-pull-request jobs and group the listed failures by cause, beginning with the repeated test and infrastructure failures. Done means the identified CI failures are addressed and the affected jobs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100