CI Reliability 2026-01-09
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/70640 to node-test-pull-request/70730 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-09.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-09 00:12 | 4 | 9 | 17 | 14 | 56 | 10.98% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-09.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(2) -
fatal error: too many errors emitted, stopping now [-ferror-limit=](4) -
fatal error: Killed signal terminated program cc1plus(3) -
Failed to trigger node-test-commit(2) -
sequential/test-performance-eventloopdelay(5) -
node-api/test_threadsafe_function/test(4) -
parallel/test-repl-programmatic-history(4) -
parallel/test-zlib-brotli-16GB(4) -
async-hooks/test-improper-order(2) -
es-module/test-esm-loader-hooks(2) -
parallel/test-buffer-slow(2) -
parallel/test-crypto-cipheriv-decipheriv(2) -
parallel/test-domain-error-types(2) -
parallel/test-quic-test-client(2) -
test-runner/test-run-watch-run-duration(2) -
wpt/test-url(2) -
wpt/test-wasm-webapi(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
Open reports/2026-01-09.md and review the linked node-test-pull-request runs from 70640 through 70730. Start with the listed failure categories and named tests, then trace their failure details in the report. Done means the listed CI failures have been investigated and the corresponding progress items are updated.
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
- 35/100