CI Reliability 2025-08-20
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/68659 to node-test-pull-request/68759 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-20.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-08-20 00:11 | 0 | 0 | 32 | 4 | 64 | 0.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-20.md to see failure details
Progress
-
sequential/test-single-executable-application(8) -
sequential/test-single-executable-application-assets(8) -
sequential/test-single-executable-application-assets-raw(8) -
sequential/test-single-executable-application-disable-experimental-sea-warning(8) -
sequential/test-single-executable-application-exec-argv(8) -
sequential/test-single-executable-application-exec-argv-empty(8) -
sequential/test-single-executable-application-snapshot(8) -
sequential/test-single-executable-application-snapshot-and-code-cache(8) -
sequential/test-single-executable-application-snapshot-worker(8) -
sequential/test-single-executable-application-use-code-cache(8) -
parallel/test-runner-mock-timers-scheduler(6) -
parallel/test-esm-loader-hooks-inspect-wait(4) -
parallel/test-http-keep-alive-empty-line(4) -
parallel/test-http-outgoing-end-cork(4) -
wasi/test-wasi(4) -
parallel/test-crypto-dh-generate-keys(3) -
parallel/test-npm-install(3) -
sequential/test-performance-eventloopdelay(3) -
parallel/test-debugger-break(2) -
parallel/test-debugger-random-port(2) -
parallel/test-fs-cp-sync-preserve-timestamps-readonly(2) -
parallel/test-fs-stat-bigint(2) -
parallel/test-http-client-close-with-default-agent(2) -
parallel/test-performance-eventlooputil(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
wpt/test-streams(2) -
Build timed out (after 30 minutes). Marking the build as failed.(8) -
fatal: No rebase in progress?(4)
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-20.md and the linked CI jobs, using the listed failing test names to organize the investigation. Review the failures from the ncu-ci walk pr report and determine which failures or timeout conditions are addressed; done means the reported CI failures are resolved or clearly accounted for.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100