CI Reliability 2025-08-26
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/68768 to node-test-pull-request/68867 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-26 00:11 | 0 | 0 | 28 | 10 | 62 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-26.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: 1572969, exit value: 1(2) -
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 1574737, exit value: 1(2) -
fatal error: ld terminated with signal 9 [Killed](8) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
fatal: No rebase in progress?(2) -
parallel/test-fastutf8stream-flush-mocks(14) -
parallel/test-fastutf8stream-sync(14) -
parallel/test-max-old-space-size-percentage(14) -
parallel/test-inspector-network-fetch(13) -
parallel/test-http-keep-alive-empty-line(5) -
wpt/test-streams(5) -
parallel/test-fs-write-stream-eagain(4) -
parallel/test-buffer-tostring-rangeerror(3) -
parallel/test-buffer-zero-fill-reset(3) -
parallel/test-child-process-advanced-serialization-splitted-length-field(3) -
parallel/test-debugger-breakpoint-exists(3) -
parallel/test-http-outgoing-end-cork(3) -
parallel/test-http2-close-while-writing(3) -
parallel/test-runner-mock-timers-scheduler(3) -
parallel/test-without-async-context-frame(3) -
async-hooks/test-improper-order(2) -
parallel/test-crypto-dh-generate-keys(2) -
parallel/test-debugger-auto-resume(2) -
parallel/test-debugger-break(2) -
parallel/test-debugger-exec(2) -
parallel/test-debugger-exec-scope(2) -
parallel/test-debugger-extract-function-name(2) -
parallel/test-repl-preview(2) -
parallel/test-runner-watch-mode-kill-signal(2) -
parallel/test-snapshot-reproducible(2) -
sequential/test-performance-eventloopdelay(2) -
sequential/test-single-executable-application(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/2025-08-26.md and the linked node-test-pull-request Jenkins runs, then group the repeated failures by the listed test or CI error. The issue is done when the tracked timeout, process, linker, report, rebase, and test failures have been investigated and the affected CI runs are green.
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
- 25/100