CI Reliability 2026-05-08
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/73148 to node-test-pull-request/73245 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-08.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-08 00:28 | 0 | 11 | 6 | 19 | 64 | 13.58% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-08.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
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) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(7) -
fatal: No rebase in progress?(7) -
parallel/test-process-finalization(7) -
sequential/test-debugger-pid(6) -
sequential/test-watch-mode-worker(6) -
parallel/test-dgram-udp6-link-local-address(5) -
parallel/test-sqlite-database-sync(5) -
test-runner/test-run-watch-dependency-repeatedly(4) -
sequential/test-gc-http-client-onerror(3) -
sequential/test-perf-hooks(3) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-memory-usage(2) -
test-runner/test-run-watch-run-duration(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-08.md and the linked Jenkins runs from node-test-pull-request/73148 through 73245 to review the failure details. Triage the listed recurring failures, beginning with the highest counts and the Progress checklist. Done means each failure has been investigated and the corresponding checklist item is resolved or 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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100