CI Reliability 2025-10-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/69652 to node-test-pull-request/69750 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-16 00:10 | 1 | 2 | 34 | 1 | 62 | 2.04% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-16.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(4) -
parallel/test-without-async-context-frame(18) -
sequential/test-worker-prof(16) -
parallel/test-runner-output(10) -
parallel/test-runner-watch-mode-kill-signal(10) -
parallel/test-quic-test-client(7) -
parallel/test-http2-close-while-writing(6) -
sequential/test-perf-hooks(6) -
wpt/test-hr-time(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(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 by reading reports/2025-10-16.md and the linked CI run details for the listed failures, including the timeout and test cases such as parallel/test-runner-output. Reproduce the affected failures and trace their causes across the CI runs; done means the recurring failures are addressed and the affected pull requests pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, 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