CI Reliability 2025-08-29
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/68854 to node-test-pull-request/68952 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-29.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-29 00:11 | 1 | 0 | 26 | 5 | 68 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-29.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(5) -
Build timed out (after 60 minutes). Marking the build as failed.(4) -
Unexpected termination of the channel(2) -
fatal error: ld terminated with signal 9 [Killed](9) -
parallel/test-inspector-network-fetch(25) -
parallel/test-runner-run-watch(5) -
sequential/test-performance-eventloopdelay(5) -
wpt/test-url(5) -
sequential/test-single-executable-application(4) -
sequential/test-single-executable-application-assets(4) -
sequential/test-single-executable-application-assets-raw(4) -
sequential/test-single-executable-application-disable-experimental-sea-warning(4) -
sequential/test-single-executable-application-exec-argv(4) -
sequential/test-single-executable-application-exec-argv-empty(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) -
sequential/test-single-executable-application-snapshot(4) -
sequential/test-single-executable-application-snapshot-and-code-cache(4) -
sequential/test-single-executable-application-snapshot-worker(4) -
sequential/test-single-executable-application-use-code-cache(4) -
parallel/test-fastutf8stream-flush-mocks(3) -
parallel/test-fastutf8stream-sync(3) -
parallel/test-http-keep-alive-empty-line(3) -
parallel/test-http-outgoing-end-cork(3) -
wpt/test-streams(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
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-esm-loader-hooks-inspect-wait(2) -
parallel/test-http-client-close-with-default-agent(2) -
parallel/test-runner-output(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 the linked node-test-pull-request jobs and the failure details in reports/2025-08-29.md. Investigate the listed timeout, linker, and test failures across the affected CI runs; done means the recurring failures are addressed and the relevant CI jobs return successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, 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