CI Reliability 2025-08-28
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/68838 to node-test-pull-request/68937 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-28 00:11 | 0 | 0 | 27 | 5 | 68 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-28.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(4) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
fatal error: ld terminated with signal 9 [Killed](10) -
parallel/test-inspector-network-fetch(26) -
parallel/test-fastutf8stream-flush-mocks(9) -
parallel/test-fastutf8stream-sync(9) -
parallel/test-max-old-space-size-percentage(7) -
parallel/test-runner-run-watch(5) -
sequential/test-single-executable-application(5) -
sequential/test-single-executable-application-assets(5) -
sequential/test-single-executable-application-assets-raw(5) -
sequential/test-single-executable-application-disable-experimental-sea-warning(5) -
sequential/test-single-executable-application-exec-argv(5) -
sequential/test-single-executable-application-exec-argv-empty(5) -
sequential/test-single-executable-application-snapshot(5) -
sequential/test-single-executable-application-snapshot-and-code-cache(5) -
sequential/test-single-executable-application-snapshot-worker(5) -
sequential/test-single-executable-application-use-code-cache(5) -
wpt/test-url(5) -
parallel/test-fs-write-stream-eagain(4) -
sequential/test-single-executable-application-exec-argv-extension-cli(4) -
sequential/test-single-executable-application-exec-argv-extension-env(4) -
sequential/test-single-executable-application-exec-argv-extension-none(4) -
wpt/test-streams(4) -
parallel/test-http-keep-alive-empty-line(3) -
parallel/test-http-outgoing-end-cork(3) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-crypto-dh-generate-keys(2) -
parallel/test-debugger-break(2) -
parallel/test-debugger-use-strict(2) -
parallel/test-debugger-watchers(2) -
parallel/test-http-client-close-with-default-agent(2) -
parallel/test-snapshot-reproducible(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-28.md and the linked node-test-pull-request runs to inspect the failure details. Triage the repeated timeout, linker, and test failures listed in Progress; done means the identified CI failures are addressed and the progress items can be checked off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100