CI Reliability 2026-05-14
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/73330 to node-test-pull-request/73429 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-14 00:34 | 0 | 8 | 13 | 6 | 73 | 8.51% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-14.md to see failure details
Progress
-
sh: line 12: [: -gt: unary operator expected(8) -
fatal: No rebase in progress?(5) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(4) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](4) -
ERROR: out of memory(3) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers_host.vcxproj](2) -
error: remote GitHub already exists.(2) -
sequential/test-watch-mode-worker(9) -
parallel/test-memory-usage(7) -
parallel/test-process-finalization(6) -
parallel/test-zlib-brotli-16GB(5) -
sequential/test-performance-eventloopdelay(3) -
async-hooks/test-emit-after-on-destroyed(2) -
async-hooks/test-statwatcher(2) -
parallel/test-http2-close-while-writing(2) -
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 failures listed in reports/2026-05-14.md and the CI range linked in this issue; the report was generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-14.md. Review the repeated shell, Git, compiler, memory, and Node test failures, then use the progress checklist to track which failures have been addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, node.js, 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