CI Reliability 2026-01-10
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/70650 to node-test-pull-request/70746 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-10 00:12 | 4 | 7 | 8 | 14 | 67 | 8.54% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-10.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(6) -
fatal error: too many errors emitted, stopping now [-ferror-limit=](4) -
fatal error: Killed signal terminated program cc1plus(3) -
fatal: No rebase in progress?(3) -
Failed to trigger node-test-commit(2) -
parallel/test-repl-programmatic-history(7) -
es-module/test-esm-loader-hooks(6) -
parallel/test-quic-test-client(6) -
es-module/test-esm-detect-ambiguous(5) -
es-module/test-esm-loader-programmatically(5) -
es-module/test-esm-loader-spawn-promisified(5) -
node-api/test_threadsafe_function/test(5) -
parallel/test-zlib-brotli-16GB(5) -
sequential/test-performance-eventloopdelay(5) -
es-module/test-esm-initialization(4) -
es-module/test-esm-loader(4) -
es-module/test-esm-loader-side-effect(4) -
es-module/test-esm-preserve-symlinks-not-found(4) -
es-module/test-esm-preserve-symlinks-not-found-plain(4) -
async-hooks/test-improper-order(2) -
parallel/test-buffer-slow(2) -
parallel/test-crypto-cipheriv-decipheriv(2) -
parallel/test-debugger-invalid-json(2) -
parallel/test-domain-error-types(2) -
test-runner/test-run-watch-emit-restarted(2) -
test-runner/test-run-watch-run-duration(2) -
wpt/test-blob(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
Start with reports/2026-01-10.md and the Jenkins runs from node-test-pull-request/70650 through 70746. Review the repeated errors and named tests, then use the ncu-ci walk command shown in the issue to investigate failures. Done means the listed recurring CI failures have been addressed and the reliability report no longer shows them recurring.
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