CI Reliability 2026-08-09
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/75561 to node-test-pull-request/75665 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-09.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-08-09 00:12 | 3 | 22 | 13 | 12 | 50 | 25.88% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-08-09.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(2) -
error: could not apply 61890720c8a... add readme and initial code(10) -
fatal: No rebase in progress?(4) -
sh: line 12: [: -gt: unary operator expected(4) -
ERROR: out of memory(2) -
Failed to trigger node-test-commit(2) -
parallel/test-stream-pipeline-http2(17) -
parallel/test-worker-terminate-http2-respond-with-file(11) -
parallel/test-sqlite-backup(3) -
test-runner/test-run-watch-cwd-isolation-none-argv(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-09.md and the failures listed in this issue; use the referenced node-test-pull-request jobs and ncu-ci walk pr --stats=true --markdown reports/2026-08-09.md output to trace each recurring failure. Done means the listed CI failures have been investigated and the affected jobs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100