CI Reliability 2025-11-02
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/69896 to node-test-pull-request/69995 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-02.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-02 00:12 | 0 | 21 | 13 | 0 | 66 | 21.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-02.md to see failure details
Progress
-
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex(9) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(8) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8(8) -
parallel/test-perf-hooks-timerify(8) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2(6) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64(5) -
parallel/test-watch-mode-files_watcher(5) -
sequential/test-worker-prof(5) -
es-module/test-esm-wasm(4) -
parallel/test-quic-test-client(4) -
parallel/test-watch-mode-kill-signal-override(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-ascii(3) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary(3) -
wpt/test-hr-time(3) -
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)
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-11-02.md and the linked node-test-pull-request runs, then inspect the listed failing Node test paths and their recurrence counts. Done means the reported CI failures are addressed and the progress list can be updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100