CI Reliability 2025-10-27
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/69796 to node-test-pull-request/69894 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-27.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-27 00:12 | 0 | 25 | 23 | 4 | 48 | 26.04% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-27.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) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(17) -
fatal: No rebase in progress?(5) -
sequential/test-worker-prof(7) -
parallel/test-runner-output(6) -
parallel/test-watch-mode-kill-signal-override(6) -
parallel/test-http2-close-while-writing(4) -
parallel/test-quic-test-client(4) -
sequential/test-perf-hooks(4) -
parallel/test-runner-watch-mode(3) -
parallel/test-watch-mode-kill-signal-default(3) -
async-hooks/test-emit-before-on-destroyed(2) -
parallel/test-net-connect-abort-controller(2) -
wpt/test-hr-time(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
Read the linked reports/2025-10-27.md and inspect the Jenkins runs from node-test-pull-request/69796 through 69894. Use the listed failure categories and test names to trace each recurring failure. Done means the unchecked reliability items have documented progress or resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100