CI Reliability 2025-08-14
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/68519 to node-test-pull-request/68616 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-14 00:12 | 1 | 0 | 32 | 4 | 63 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-14.md to see failure details
Progress
-
sequential/test-tls-session-timeout(14) -
wasi/test-wasi(12) -
parallel/test-http-keep-alive-empty-line(7) -
parallel/test-runner-run(6) -
parallel/test-runner-mock-timers-scheduler(5) -
sequential/test-performance-eventloopdelay(5) -
parallel/test-http-outgoing-end-cork(4) -
client-proxy/test-http-proxy-request-connection-refused(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-repl-history-navigation(2) -
parallel/test-runner-output(2) -
parallel/test-runner-watch-mode-kill-signal(2) -
parallel/test-tls-dhe(2) -
wpt/test-webcrypto(2) -
Build timed out (after 30 minutes). Marking the build as failed.(4) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
fatal: No rebase in progress?(4) -
FATAL: Channel "hudson.remoting.Channel@1907e711:JNLP4-connect connection from ... Remote call on JNLP4-connect connection from e.1a.7534.ip4.static.sl-reverse.com/52.117.26.14:53500 failed. The channel is closing down or has closed down(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-14.md and the CI runs linked in the issue, then inspect the listed failures such as sequential/test-tls-session-timeout and wasi/test-wasi. Reproduce the relevant failures in the node-test-pull-request jobs and use the failure details to determine what needs changing; done means the recurring failures are resolved and CI returns green.
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