CI Reliability 2025-08-23
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/68725 to node-test-pull-request/68824 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-23.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-23 00:11 | 0 | 0 | 36 | 8 | 56 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-23.md to see failure details
Progress
-
parallel/test-max-old-space-size-percentage(9) -
parallel/test-fastutf8stream-flush-mocks(8) -
parallel/test-fastutf8stream-sync(8) -
parallel/test-http-keep-alive-empty-line(7) -
parallel/test-runner-mock-timers-scheduler(7) -
parallel/test-http-outgoing-end-cork(6) -
parallel/test-inspector-network-fetch(5) -
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-http2-close-while-writing(3) -
parallel/test-without-async-context-frame(3) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-debugger-breakpoint-exists(2) -
parallel/test-net-autoselectfamily(2) -
parallel/test-repl-history-navigation(2) -
parallel/test-repl-preview(2) -
parallel/test-runner-watch-mode-kill-signal(2) -
parallel/test-webcrypto-wrap-unwrap(2) -
sequential/test-single-executable-application(2) -
wpt/test-streams(2) -
wpt/test-webcrypto(2) -
Build timed out (after 30 minutes). Marking the build as failed.(7) -
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?(2) -
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-23.md and the linked node-test-pull-request jobs, using the failure names listed in the issue to trace each repeated failure. Review the generated ncu-ci report and investigate the unchecked entries; done means the relevant failures have been addressed and the progress checklist is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100