CI Reliability 2026-05-17
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/73400 to node-test-pull-request/73499 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-17 00:31 | 0 | 21 | 16 | 6 | 57 | 22.34% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-17.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(3) -
sh: line 12: [: -gt: unary operator expected(13) -
fatal: No rebase in progress?(9) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(3) -
ERROR: out of memory(2) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](2) -
sequential/test-watch-mode-worker(9) -
parallel/test-http2-close-while-writing(5) -
parallel/test-zlib-brotli-16GB(3) -
sequential/test-performance-eventloopdelay(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-17.md and the linked node-test-pull-request builds 73400–73499. Review the listed failure groups and their occurrence counts, then trace each to the relevant CI job or test entry point. Done means the recurring failures have been investigated and the report's progress items are resolved or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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