CI Reliability 2025-07-11
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/67828 to node-test-pull-request/67926 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-07-11.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-07-11 00:11 | 0 | 1 | 30 | 1 | 68 | 1.01% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-07-11.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(11) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(5) -
fatal: No rebase in progress?(6) -
Failed to trigger node-test-commit(5) -
pummel/test-string-decoder-large-buffer(11) -
parallel/test-runner-watch-mode-kill-signal(7) -
es-module/test-esm-loader-chaining(5) -
es-module/test-esm-loader-event-loop(5) -
es-module/test-esm-loader-hooks(5) -
es-module/test-esm-loader-not-found(5) -
es-module/test-vm-contextified-script-leak(5) -
parallel/test-buffer-tostring-range(5) -
parallel/test-string-decoder(5) -
sequential/test-child-process-pass-fd(5) -
parallel/test-worker-message-port-transfer-filehandle(4) -
sequential/test-debugger-invalid-args(4) -
wpt/test-streams(4) -
es-module/test-esm-loader-default-resolver(3) -
report/test-report-worker(3) -
parallel/test-child-process-advanced-serialization-splitted-length-field(2) -
parallel/test-fs-cp(2) -
parallel/test-inspector-network-fetch(2) -
parallel/test-process-threadCpuUsage-worker-threads(2) -
parallel/test-runner-run-watch(2) -
parallel/test-url-parse-invalid-input(2) -
parallel/test-v8-coverage(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
sequential/test-performance-eventloopdelay(2) -
sequential/test-tls-session-timeout(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 reports/2025-07-11.md and the node-test-pull-request builds 67828 through 67926. Investigate the listed timeout, repository-fetch, trigger, and test failures, then use the Progress checklist to track each failure until the affected CI jobs are reliable again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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