CI Reliability 2025-08-13
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/68499 to node-test-pull-request/68597 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-13.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-13 00:12 | 0 | 0 | 30 | 4 | 66 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-13.md to see failure details
Progress
-
sequential/test-tls-session-timeout(16) -
wasi/test-wasi(11) -
parallel/test-runner-run(7) -
parallel/test-http-keep-alive-empty-line(6) -
sequential/test-performance-eventloopdelay(6) -
parallel/test-runner-mock-timers-scheduler(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-watch-mode-kill-signal(2) -
parallel/test-tls-dhe(2) -
sequential/test-perf-hooks(2) -
wpt/test-webcrypto(2) -
Build timed out (after 30 minutes). Marking the build as failed.(5) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
fatal: No rebase in progress?(3) -
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-13.md and the linked CI jobs to inspect the failure details, then review the listed tests such as sequential/test-tls-session-timeout and wasi/test-wasi. Use the generated ncu-ci report to trace recurring failures; done means the failures in the progress list have been investigated and their status updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100