CI Reliability 2025-10-17
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/69670 to node-test-pull-request/69766 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-17 00:11 | 1 | 2 | 33 | 1 | 63 | 2.04% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-17.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(2) -
sequential/test-worker-prof(19) -
parallel/test-without-async-context-frame(16) -
parallel/test-quic-test-client(9) -
parallel/test-runner-output(9) -
parallel/test-runner-watch-mode-kill-signal(9) -
sequential/test-perf-hooks(5) -
wpt/test-hr-time(4) -
parallel/test-http2-close-while-writing(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-gc-http-client-connaborted(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-17.md and the linked CI runs from node-test-pull-request/69670 through 69766. Investigate the listed failures, beginning with the most frequent tests such as sequential/test-worker-prof and parallel/test-without-async-context-frame. Done means the failure causes are addressed and the affected CI jobs no longer fail repeatedly.
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