CI Reliability 2025-10-28
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/69815 to node-test-pull-request/69912 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-28 00:10 | 4 | 22 | 21 | 4 | 49 | 23.91% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-28.md to see failure details
Progress
-
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 938203, exit value: 1(3) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(15) -
fatal: No rebase in progress?(2) -
sequential/test-worker-prof(6) -
parallel/test-runner-output(5) -
parallel/test-watch-mode-kill-signal-override(5) -
parallel/test-http2-close-while-writing(3) -
parallel/test-quic-test-client(3) -
parallel/test-runner-watch-mode(3) -
sequential/test-perf-hooks(3) -
parallel/test-net-connect-abort-controller(2) -
parallel/test-watch-mode-kill-signal-default(2) -
pummel/test-timers(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-10-28.md and the linked node-test-pull-request builds 69815 through 69912. Compare the listed CI and test failures, including the shell-spawn, workspace, runner, HTTP/2, QUIC, and watch-mode entries. Done means the identified recurring failures have been addressed and the affected CI jobs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, 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