CI Reliability 2025-10-31
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/69864 to node-test-pull-request/69963 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-31.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-10-31 00:11 | 0 | 21 | 18 | 0 | 61 | 21.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-10-31.md to see failure details
Progress
-
sequential/test-worker-prof(8) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8(7) -
parallel/test-watch-mode-kill-signal-override(6) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2(4) -
es-module/test-esm-wasm(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary(3) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex(3) -
parallel/test-perf-hooks-timerify(3) -
parallel/test-quic-test-client(3) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64(2) -
async-hooks/test-emit-before-on-destroyed(2) -
parallel/test-runner-output(2) -
parallel/test-watch-mode-files_watcher(2) -
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 938203, exit value: 1(5) -
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 957237, exit value: 1(4) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(10)
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-31.md and the linked node-test-pull-request jobs to inspect the listed recurring failures. Reproduce the affected tests, including sequential/test-worker-prof, the stringbytes-external-exceed-max tests, and the watch-mode tests, then determine which failures are actionable. Done means the identified CI failures are fixed or reliably diagnosed and the affected jobs pass.
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
- 35/100