CI Reliability 2026-05-13
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/73303 to node-test-pull-request/73397 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-13.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-13 00:32 | 2 | 7 | 9 | 4 | 78 | 7.45% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-13.md to see failure details
Progress
-
Failed to create a temp file on C:\workspace\node-compile-windows(2) -
ERROR: out of memory(3) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(3) -
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) -
sh: line 12: [: -gt: unary operator expected(2) -
parallel/test-memory-usage(12) -
parallel/test-process-finalization(10) -
sequential/test-watch-mode-worker(9) -
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 reports/2026-05-13.md and the linked node-test-pull-request Jenkins runs to identify the causes behind the listed failures. Review the generated ncu-ci walk pr report and investigate each recurring error or test failure; done means the tracked failures are resolved or otherwise explained and subsequent CI runs are reliable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, shell
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100