CI Reliability 2025-11-01
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/69882 to node-test-pull-request/69978 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-01.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-01 00:12 | 1 | 20 | 16 | 0 | 63 | 20.20% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-01.md to see failure details
Progress
-
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8(7) -
parallel/test-perf-hooks-timerify(7) -
sequential/test-worker-prof(7) -
parallel/test-watch-mode-kill-signal-override(6) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(5) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2(5) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex(4) -
es-module/test-esm-wasm(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64(3) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary(3) -
async-hooks/test-emit-before-on-destroyed(2) -
parallel/test-quic-test-client(2) -
parallel/test-runner-output(2) -
parallel/test-watch-mode-files_watcher(2) -
parallel/test-watch-mode-kill-signal-default(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 ...(12)
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 and the Jenkins job range referenced in the issue, then review the listed failing tests and CI errors. Done means the reported failures have been investigated and the corresponding checklist entries can be updated; the issue does not identify a specific fix or entry point.
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