CI Reliability 2025-11-03
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/69919 to node-test-pull-request/70016 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-11-03.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-11-03 00:12 | 0 | 23 | 12 | 1 | 64 | 23.23% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-11-03.md to see failure details
Progress
-
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max(11) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex(9) -
parallel/test-perf-hooks-timerify(9) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8(8) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64(6) -
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-ascii(5) -
parallel/test-watch-mode-files_watcher(5) -
parallel/test-watch-mode-kill-signal-override(5) -
parallel/test-quic-test-client(4) -
sequential/test-worker-prof(4) -
addons/stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary(3) -
wpt/test-hr-time(3) -
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: remote GitHub already exists.(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 the linked CI job range and the failure details in reports/2025-11-03.md, then investigate the listed failing tests and execution errors. Done means the reported recurring failures are addressed and the affected CI runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, 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
- 25/100