CI Reliability 2025-10-11
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/69578 to node-test-pull-request/69676 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-11.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-11 00:10 | 1 | 0 | 25 | 4 | 70 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-11.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(3) -
Failed to trigger node-test-commit(2) -
fatal error: ld terminated with signal 9 [Killed](2) -
parallel/test-without-async-context-frame(23) -
sequential/test-worker-prof(16) -
parallel/test-http2-close-while-writing(12) -
sequential/test-perf-hooks(12) -
parallel/test-runner-watch-mode-kill-signal(9) -
client-proxy/test-https-proxy-request-invalid-char-in-url(6) -
wpt/test-hr-time(5) -
parallel/test-quic-test-client(4) -
parallel/test-cluster-fork-stdio(2) -
parallel/test-fs-watch-recursive-delete(2) -
parallel/test-runner-output(2) -
parallel/test-zlib-brotli-16GB(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/2025-10-11.md and the linked node-test-pull-request jobs, then review the listed recurring failures and test names. Determine which failures are reproducible and address the affected CI or tests; done should mean the reported failures no longer recur and the Progress checklist is 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
- 25/100