CI Reliability 2026-01-16
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/70722 to node-test-pull-request/70819 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-16 00:12 | 0 | 10 | 19 | 6 | 65 | 10.64% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-16.md to see failure details
Progress
-
node-api/test_threadsafe_function/test(12) -
parallel/test-repl-programmatic-history(11) -
es-module/test-esm-detect-ambiguous(5) -
es-module/test-esm-loader-hooks(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) -
test-runner/test-run-watch-cwd-isolation-none(4) -
parallel/test-crypto-dh-generate-keys(3) -
wpt/test-wasm-webapi(3) -
async-hooks/test-emit-before-on-destroyed(2) -
async-hooks/test-improper-order(2) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-domain-http-server(2) -
parallel/test-http2-close-while-writing(2) -
parallel/test-zlib-brotli-16GB(2) -
test-runner/test-run-watch-repeatedly(2) -
wpt/test-streams(2) -
Build timed out (after 30 minutes). Marking the build as failed.(3) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(6) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
Failed to trigger node-test-commit(2) -
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 node-test-pull-request builds and reports/2026-01-16.md, then inspect the listed recurring test and infrastructure failures. Progress is complete when the reported failures have been investigated and the corresponding checklist entries can be updated.
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
- 35/100