CI Reliability 2026-03-04
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/71452 to node-test-pull-request/71551 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-03-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-03-04 00:15 | 0 | 17 | 30 | 2 | 51 | 17.35% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-03-04.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(5) -
sh: line 12: [: -gt: unary operator expected(5) -
Failed to trigger node-test-commit(4) -
error C2099: initializer is not a constant [C:\workspace\node-compile-windows\node\deps\brotli\brotli.vcxproj](2) -
Unexpected termination of the channel(8) -
parallel/test-debugger-heap-profiler(4) -
sequential/test-performance-eventloopdelay(4) -
parallel/test-child-process-fork-exec-path(3) -
parallel/test-file-write-stream4(3) -
parallel/test-fs-write-stream-eagain(3) -
parallel/test-http-client-response-domain(3) -
parallel/test-module-loading-globalpaths(3) -
parallel/test-promise-reject-callback-exception(3) -
parallel/test-http2-close-while-writing(2) -
parallel/test-runner-output(2) -
sequential/test-watch-mode-restart-esm-loading-error(2) -
test-runner/test-run-watch-repeatedly(2) -
test-runner/test-run-watch-run-duration(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-03-04.md and the linked node-test-pull-request builds to inspect the listed recurring failures. Determine which failures remain reproducible and update the Progress checklist as each has an identified cause and resolution; the issue does not define a single implementation target.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100