CI Reliability 2025-09-02
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/68892 to node-test-pull-request/68989 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-02.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-02 00:11 | 0 | 7 | 30 | 4 | 59 | 7.29% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-02.md to see failure details
Progress
-
parallel/test-inspector-network-fetch(12) -
sequential/test-performance-eventloopdelay(7) -
parallel/test-runner-run-watch(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) -
es-module/test-http-imports(3) -
parallel/test-esm-loader-hooks-inspect-wait(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-domain-error-types(2) -
wpt/test-streams(2) -
Build timed out (after 30 minutes). Marking the build as failed.(5) -
Build timed out (after 60 minutes). Marking the build as failed.(5) -
Unexpected termination of the channel(4) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal error: ld terminated with signal 9 [Killed](4) -
Failed to trigger sub builds(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-09-02.md and the linked node-test-pull-request jobs, then review the listed failures using the generated ncu-ci walk report. Investigate the repeated test, timeout, repository-fetch, and build errors; done means the tracked CI failures are resolved or clearly accounted for.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100