CI Reliability 2025-10-22
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/69750 to node-test-pull-request/69847 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-22 00:11 | 2 | 18 | 13 | 2 | 65 | 18.75% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-22.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
parallel/test-without-async-context-frame(12) -
sequential/test-worker-prof(10) -
parallel/test-quic-test-client(8) -
parallel/test-runner-output(7) -
sequential/test-perf-hooks(6) -
parallel/test-runner-watch-mode-kill-signal(5) -
parallel/test-http2-close-while-writing(4) -
parallel/test-runner-watch-mode(3) -
parallel/test-watch-mode-kill-signal-default(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-watch-mode-kill-signal-override(2) -
wpt/test-hr-time(2) -
fatal: No rebase in progress?(7)
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 CI job range and read reports/2025-10-22.md for failure details. Use the listed ncu-ci command to understand how the report was generated, then investigate the failures in the Progress list. Done means the recurring failures are addressed or explained and subsequent CI runs are reliable.
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
- Mostly clear
- Newbie friendliness
- 30/100