CI Reliability 2025-08-17
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/68575 to node-test-pull-request/68669 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-17 00:13 | 0 | 0 | 34 | 10 | 56 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-17.md to see failure details
Progress
-
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?(3) -
ERROR: Step ?Publish JUnit test result report? failed: no workspace for ...(2) -
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) -
wasi/test-wasi(13) -
parallel/test-http-keep-alive-empty-line(7) -
parallel/test-runner-mock-timers-scheduler(6) -
parallel/test-crypto-dh-generate-keys(4) -
parallel/test-esm-loader-hooks-inspect-wait(4) -
parallel/test-npm-install(4) -
sequential/test-performance-eventloopdelay(4) -
parallel/test-http-outgoing-end-cork(3) -
client-proxy/test-http-proxy-request-connection-refused(2) -
parallel/test-performance-eventlooputil(2) -
wpt/test-streams(2) -
wpt/test-webcrypto(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 the linked reliability report at reports/2025-08-17.md and the Jenkins node-test-pull-request builds 68575–68669. Review the failure details for the listed test names and infrastructure errors before deciding which failures are actionable. Done means the relevant recurring CI failures are addressed and the affected checks no longer reproduce.
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