CI Reliability 2026-05-12
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/73283 to node-test-pull-request/73382 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-12 00:30 | 0 | 4 | 7 | 3 | 86 | 4.12% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-12.md to see failure details
Progress
-
ERROR: out of memory(2) -
parallel/test-memory-usage(14) -
parallel/test-process-finalization(13) -
sequential/test-watch-mode-worker(6) -
parallel/test-zlib-brotli-16GB(3) -
sequential/test-performance-eventloopdelay(3) -
test-runner/test-output-test-runner-watch-spec(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
test-runner/test-run-watch-emit-restarted(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 the linked CI jobs from node-test-pull-request/73283 through 73382 and the generated reports/2026-05-12.md failure details. Review the listed failures, including parallel/test-memory-usage and sequential/test-watch-mode-worker, then use the relevant CI output to identify fixes; done means the recurring failures are addressed and the affected checks pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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