CI Reliability 2025-09-01
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/68878 to node-test-pull-request/68976 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-01.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-01 00:13 | 0 | 5 | 30 | 4 | 61 | 5.21% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-01.md to see failure details
Progress
-
parallel/test-inspector-network-fetch(15) -
sequential/test-performance-eventloopdelay(6) -
wpt/test-url(5) -
parallel/test-runner-run-watch(4) -
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) -
wpt/test-streams(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
es-module/test-http-imports(2) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
parallel/test-http-client-close-with-default-agent(2) -
parallel/test-http-keep-alive-empty-line(2) -
parallel/test-http-outgoing-end-cork(2) -
parallel/test-runner-output(2) -
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](6)
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 reliability report and the listed failures, including parallel/test-inspector-network-fetch, sequential/test-performance-eventloopdelay, and the single-executable-application tests. Reproduce the reported CI failures, determine their causes, and consider the work done when the listed failure entries are resolved and can be checked off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100