CI Reliability 2026-01-21
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/70840 to node-test-pull-request/70933 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-21.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-21 00:12 | 0 | 19 | 22 | 0 | 59 | 19.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-21.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(14) -
parallel/test-http2-close-while-writing(5) -
parallel/test-quic-test-client(4) -
sequential/test-watch-mode-restart-esm-loading-error(4) -
test-runner/test-run-watch-repeatedly(4) -
async-hooks/test-emit-before-on-destroyed(3) -
parallel/test-runner-output(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
node-api/test_threadsafe_function/test(2) -
parallel/test-fs-promises-watch-iterator(2) -
parallel/test-http-request-host-header(2) -
parallel/test-zlib-brotli-16GB(2) -
pummel/test-repl-paste-big-data(2) -
test-runner/test-run-watch-cwd-isolation-none(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
test-runner/test-run-watch-emit-restarted(2) -
test-runner/test-run-watch-without-file(2) -
ERROR: Error fetching remote repo 'origin'(4) -
fatal: No rebase in progress?(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 the linked reports/2026-01-21.md and the Jenkins failures from jobs 70840–70933. Review each listed test or repository error, then use the corresponding Node.js CI jobs to investigate them. Done means the recurring failures listed in the issue are resolved and no longer affect multiple pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, 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
- 32/100