CI Reliability 2026-05-07
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/73120 to node-test-pull-request/73219 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-07.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-07 00:28 | 0 | 10 | 4 | 32 | 54 | 14.71% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-07.md to see failure details
Progress
-
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): Failed to exec spawn helper: pid: 3280872, exit code: 1, error: 0 (none)(2) -
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 818939, exit value: 1(2) -
fatal: No rebase in progress?(5) -
parallel/test-process-finalization(6) -
sequential/test-watch-mode-worker(5) -
parallel/test-sqlite-database-sync(4) -
sequential/test-debugger-pid(4) -
sequential/test-performance-eventloopdelay(4) -
parallel/test-dgram-udp6-link-local-address(3) -
sequential/test-gc-http-client-onerror(3) -
sequential/test-perf-hooks(3) -
test-runner/test-run-watch-run-duration(3) -
test-runner/test-run-watch-dependency-repeatedly(2) -
test-runner/test-run-watch-repeatedly(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 reports/2026-05-07.md and the linked node-test-pull-request runs; review the failure details and the progress entries listed here. Use the affected test names and failure messages to trace each problem. Done means the listed recurring failures are investigated and the corresponding progress items are resolved or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100