CI Reliability 2025-05-27
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/67020 to node-test-pull-request/67124 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-27.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-05-27 00:11 | 1 | 12 | 9 | 4 | 74 | 12.63% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-05-27.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(6) -
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 3297692, exit value: 1(3) -
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 3306322, exit value: 1(3) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(7) -
parallel/test-http2-debug(23) -
parallel/test-buffer-tostring-range(10) -
pummel/test-blob-slice-with-large-size(10) -
parallel/test-buffer-tostring-rangeerror(7) -
wpt/test-streams(7) -
parallel/test-buffer-writefloat(5) -
parallel/test-buffer-zero-fill-reset(5) -
parallel/test-child-process-advanced-serialization-splitted-length-field(5) -
parallel/test-child-process-constructor(5) -
parallel/test-runner-run-watch(5) -
sequential/test-performance-eventloopdelay(5) -
async-hooks/test-emit-after-on-destroyed(4) -
async-hooks/test-improper-unwind(4) -
parallel/test-stream-readable-to-web(3) -
parallel/test-zlib-brotli-16GB(3) -
sequential/test-tls-session-timeout(3)
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-05-27.md and the linked node-test-pull-request builds 67020 through 67124. Group the repeated timeout, fetch, shell-spawn, rebase, and test failures, then inspect the listed CI results for evidence of their causes. Done means the applicable entries in the Progress checklist have been investigated and resolved or clearly documented.
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
- 28/100