CI Reliability 2026-05-16
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/73386 to node-test-pull-request/73484 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-16 00:29 | 1 | 18 | 15 | 7 | 59 | 19.57% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-16.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(3) -
sh: line 12: [: -gt: unary operator expected(12) -
fatal: No rebase in progress?(7) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(5) -
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 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(11) -
parallel/test-http2-close-while-writing(5) -
parallel/test-zlib-brotli-16GB(3) -
sequential/test-performance-eventloopdelay(2) -
sequential/test-watch-mode-restart-esm-loading-error(2) -
test-runner/test-run-watch-repeatedly(2) -
test-runner/test-run-watch-without-file(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-16.md and the failures linked from node-test-pull-request/73386 through 73484. Review the generated ncu-ci walk pr --stats=true --markdown reports/2026-05-16.md output and group the listed errors and failing tests before choosing a scope. Done means the selected recurring CI failures are addressed and the affected checks no longer fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100