CI Reliability 2025-08-12
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/68473 to node-test-pull-request/68571 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-12 00:12 | 1 | 0 | 28 | 3 | 68 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-12.md to see failure details
Progress
-
sequential/test-tls-session-timeout(25) -
wasi/test-wasi(10) -
parallel/test-runner-run(8) -
sequential/test-performance-eventloopdelay(8) -
parallel/test-http-keep-alive-empty-line(5) -
parallel/test-runner-mock-timers-scheduler(5) -
client-proxy/test-http-proxy-request-connection-refused(3) -
parallel/test-http-outgoing-end-cork(3) -
parallel/test-repl-preview(3) -
client-proxy/test-https-proxy-request-connection-refused(2) -
parallel/test-http-server-headers-timeout-keepalive(2) -
parallel/test-runner-output(2) -
parallel/test-runner-watch-mode-kill-signal(2) -
parallel/test-tls-dhe(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
sequential/test-perf-hooks(2) -
Build timed out (after 30 minutes). Marking the build as failed.(9) -
Build timed out (after 60 minutes). Marking the build as failed.(3)
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-08-12.md and the CI links for node-test-pull-request/68473 through 68571, then review the listed failing tests and timeout entries. Reproduce the reported failures and trace each one to its cause. Done means the progress items are resolved and the affected CI runs no longer fail or time out.
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