CI Reliability 2025-10-14
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/69617 to node-test-pull-request/69716 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-14 00:10 | 1 | 1 | 33 | 1 | 64 | 1.02% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-14.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(3) -
parallel/test-without-async-context-frame(19) -
sequential/test-worker-prof(18) -
parallel/test-http2-close-while-writing(13) -
sequential/test-perf-hooks(10) -
parallel/test-runner-watch-mode-kill-signal(9) -
parallel/test-quic-test-client(6) -
parallel/test-runner-output(6) -
wpt/test-hr-time(6) -
client-proxy/test-https-proxy-request-invalid-char-in-url(4) -
parallel/test-cluster-fork-stdio(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-14.md and the linked node-test-pull-request jobs covering builds 69617 through 69716. Use the listed failure names as entry points for investigating each CI failure across the affected tests. Done means the failures are explained or fixed and the Progress checklist reflects their resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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
- 25/100