CI Reliability 2026-01-12
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/70676 to node-test-pull-request/70775 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-12 00:13 | 3 | 9 | 9 | 11 | 68 | 10.47% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-12.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(10) -
node-api/test_threadsafe_function/test(8) -
es-module/test-esm-loader-hooks(6) -
es-module/test-esm-detect-ambiguous(5) -
es-module/test-esm-loader-programmatically(5) -
es-module/test-esm-loader-spawn-promisified(5) -
parallel/test-quic-test-client(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) -
sequential/test-performance-eventloopdelay(4) -
parallel/test-zlib-brotli-16GB(3) -
test-runner/test-run-watch-cwd-isolation-none(3) -
test-runner/test-run-watch-repeatedly(3) -
async-hooks/test-improper-order(2) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-buffer-slow(2) -
parallel/test-crypto-cipheriv-decipheriv(2) -
parallel/test-debugger-invalid-json(2) -
parallel/test-domain-error-types(2) -
parallel/test-http2-close-while-writing(2) -
test-runner/test-run-watch-emit-restarted(2) -
wpt/test-blob(2) -
wpt/test-url(2) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(5) -
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 reports/2026-01-12.md and the linked CI jobs for failure details, then inspect the listed failing tests such as parallel/test-repl-programmatic-history and es-module/test-esm-loader-hooks. Determine which failures are actionable and update the Progress checklist as they are resolved; done is addressing the failures recorded in this report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100