CI Reliability 2025-08-24
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/68740 to node-test-pull-request/68839 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-24.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-24 00:12 | 1 | 0 | 34 | 10 | 55 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-24.md to see failure details
Progress
-
parallel/test-max-old-space-size-percentage(11) -
parallel/test-fastutf8stream-flush-mocks(10) -
parallel/test-fastutf8stream-sync(10) -
parallel/test-inspector-network-fetch(7) -
parallel/test-runner-mock-timers-scheduler(7) -
parallel/test-http-keep-alive-empty-line(6) -
parallel/test-http-outgoing-end-cork(6) -
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-fs-write-stream-eagain(3) -
parallel/test-http2-close-while-writing(3) -
parallel/test-without-async-context-frame(3) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-debugger-break(2) -
parallel/test-debugger-breakpoint-exists(2) -
parallel/test-repl-preview(2) -
parallel/test-runner-watch-mode-kill-signal(2) -
wpt/test-streams(2) -
Build timed out (after 30 minutes). Marking the build as failed.(5) -
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) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
fatal error: ld terminated with signal 9 [Killed](3) -
fatal: No rebase in progress?(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-24.md and the linked CI builds from node-test-pull-request/68740 through 68839. Review the logs for the unchecked test and infrastructure failures, then determine whether each is reproducible or environmental. Done means the listed recurring failures are resolved or documented with the relevant CI evidence.
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