CI Reliability 2025-08-01
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/68241 to node-test-pull-request/68338 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-01.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-01 00:14 | 1 | 0 | 27 | 7 | 65 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-01.md to see failure details
Progress
-
sequential/test-tls-session-timeout(15) -
wasi/test-wasi(10) -
sequential/test-performance-eventloopdelay(7) -
parallel/test-http-keep-alive-empty-line(6) -
parallel/test-runner-mock-timers-scheduler(6) -
parallel/test-http-outgoing-end-cork(5) -
parallel/test-cli-eval(4) -
parallel/test-cli-node-print-help(4) -
parallel/test-http-server-headers-timeout-keepalive(4) -
parallel/test-stream-readable-to-web(4) -
client-proxy/test-http-proxy-request-connection-refused(3) -
client-proxy/test-https-proxy-request-connection-refused(3) -
parallel/test-http2-forget-closed-streams(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-async-context-frame(2) -
parallel/test-debugger-exceptions(2) -
parallel/test-http-client-close-with-default-agent(2) -
parallel/test-runner-output(2) -
parallel/test-runner-run-watch(2) -
sequential/test-perf-hooks(2) -
Build timed out (after 30 minutes). Marking the build as failed.(6) -
fatal: No rebase in progress?(4) -
sh: line 1: 429:: command not found(4) -
Error: - process terminated with status 1, expected 0(2) -
Failed to trigger node-test-commit(2) -
Unknown(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-08-01.md and the linked CI jobs to inspect the listed failures. Investigate the affected test names and infrastructure errors, then use the Progress checklist to record which failures have been addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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