CI Reliability 2026-03-06
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/71494 to node-test-pull-request/71588 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-03-06.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-03-06 00:20 | 0 | 18 | 27 | 3 | 52 | 18.56% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-03-06.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(3) -
sh: line 12: [: -gt: unary operator expected(7) -
fatal: No rebase in progress?(5) -
error C2099: initializer is not a constant [C:\workspace\node-compile-windows\node\deps\brotli\brotli.vcxproj](2) -
Unexpected termination of the channel(7) -
parallel/test-child-process-fork-exec-path(6) -
parallel/test-file-write-stream4(6) -
parallel/test-http-client-response-domain(6) -
parallel/test-module-loading-globalpaths(6) -
parallel/test-promise-reject-callback-exception(6) -
sequential/test-performance-eventloopdelay(5) -
test-runner/test-run-watch-without-file(3) -
parallel/test-domain-error-types(2) -
parallel/test-http2-close-while-writing(2) -
parallel/test-runner-output(2) -
parallel/test-zlib-brotli-16GB(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)
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 by reading reports/2026-03-06.md and the linked node-test-pull-request jobs, then use ncu-ci walk pr --stats=true --markdown reports/2026-03-06.md to inspect the listed failures. Done means identifying and resolving the reported CI failures so the affected PRs no longer fail for these reasons and the progress list can be updated.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100