CI Reliability 2025-08-03
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/68277 to node-test-pull-request/68375 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-03.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-03 00:13 | 0 | 0 | 25 | 9 | 66 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-03.md to see failure details
Progress
-
sequential/test-tls-session-timeout(25) -
sequential/test-performance-eventloopdelay(8) -
wasi/test-wasi(6) -
parallel/test-cli-eval(4) -
parallel/test-cli-node-print-help(4) -
parallel/test-runner-mock-timers-scheduler(4) -
parallel/test-crypto-dh-generate-keys(3) -
parallel/test-stream-readable-to-web(3) -
client-proxy/test-http-proxy-request-connection-refused(2) -
client-proxy/test-https-proxy-request-connection-refused(2) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-debugger-exceptions(2) -
parallel/test-http-keep-alive-empty-line(2) -
parallel/test-http-outgoing-end-cork(2) -
parallel/test-http2-forget-closed-streams(2) -
wpt/test-streams(2) -
wpt/test-webcrypto(2) -
Build timed out (after 30 minutes). Marking the build as failed.(5) -
fatal: No rebase in progress?(4) -
sh: line 1: 429:: command not found(3) -
Failed to trigger node-test-commit(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 opening reports/2025-08-03.md and the linked node-test-pull-request runs to inspect the listed failures. Work through the recurring test, timeout, rebase, and trigger errors in the report; done means the listed reliability problems are addressed and the affected CI runs are green.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100