CI Reliability 2026-01-23
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/70883 to node-test-pull-request/70977 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-23.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-23 00:13 | 1 | 16 | 23 | 1 | 59 | 16.33% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-23.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(13) -
parallel/test-inspector-network-http2-compressed(6) -
sequential/test-watch-mode-restart-esm-loading-error(5) -
test-runner/test-run-watch-repeatedly(4) -
node-api/test_threadsafe_function/test(3) -
parallel/test-fs-watch-recursive-delete(3) -
parallel/test-http2-close-while-writing(3) -
parallel/test-quic-test-client(3) -
parallel/test-zlib-brotli-16GB(3) -
wpt/test-streams(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-fs-promises-watch-iterator(2) -
parallel/test-http-request-host-header(2) -
parallel/test-timers-immediate-queue(2) -
pummel/test-repl-paste-big-data(2) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-run-watch-cwd-isolation-none(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
test-runner/test-run-watch-without-file(2) -
wpt/test-hr-time(2) -
ERROR: Error fetching remote repo 'origin'(4) -
Failed to trigger node-test-commit(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-01-23.md and the linked CI runs to inspect failure details for the listed tests and infrastructure errors. Triage one recurring failure first, then run its named test or reproduce the CI error; done means the selected failure is fixed and its progress item is checked.
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
- 32/100