You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inspected only run 40070857537, job 120806222445, Test Suite - Rust (3/4), attempt 1, for PR #6313, head bd997efc9952c024a85c9f5e8084c4ebbb5c2b10. The job API confirms attempt 1; the ticket's 1 -> 2 describes the detector transition, not another attempt inspected here.
The 10-minute job limit expired during Download Rust test archive, before tests started:
Job started at 06:53:55 UTC on October 24; setup finished at 06:54:02.
actions/download-artifact@v4 selected rust-tests-linux, 5,599,670,484 bytes (about 5.22 GiB). Download began at 06:54:03.552 UTC.
No successful download/digest/extraction completion followed. At 07:03:57.947 UTC, about 9m54s later, the action reported The operation was canceled. The check-run annotation explicitly says The job has exceeded the maximum execution time of 10m0s.
The API marks the download step cancelled and Run Rust test partition skipped. No test assertion, panic, or demonstrated product hang occurred.
Visible root cause: artifact download/handling exhausted the shared job budget. This log cannot distinguish stalled network transfer, slow storage/extraction, or another artifact-action bottleneck. The Node deprecation warnings are not evidence of the cause. Measuring transfer/extraction separately, reducing the archive size, and budgeting artifact setup independently of test execution would help isolate and mitigate this failure.
Searched open and closed public issues using rust-tests-linux, Download Rust test archive, and broad artifact timeout, download cancelled, and maximum execution time terms; inspected relevant Test flakes tickets and closed-ticket timelines.
Top duplicate candidate: CI flake - Rust test archive transfer exhausts shard job budget #6330, the open consolidated tracker for Rust test archive transfer exhausting the shard job budget. Same download-stage cancellation, ten-minute limit, multi-GiB archive, and tests never starting. This matches the observable mechanism; the underlying transfer bottleneck remains unproven.
Activity
clockwork-labs-bot commentedon Oct 24, 2026
Exact-attempt diagnosis
Inspected only run 40070857537, job 120806222445, Test Suite - Rust (3/4), attempt 1, for PR #6313, head
bd997efc9952c024a85c9f5e8084c4ebbb5c2b10. The job API confirms attempt 1; the ticket's1 -> 2describes the detector transition, not another attempt inspected here.The 10-minute job limit expired during Download Rust test archive, before tests started:
actions/download-artifact@v4selectedrust-tests-linux, 5,599,670,484 bytes (about 5.22 GiB). Download began at 06:54:03.552 UTC.The operation was canceled.The check-run annotation explicitly saysThe job has exceeded the maximum execution time of 10m0s.Visible root cause: artifact download/handling exhausted the shared job budget. This log cannot distinguish stalled network transfer, slow storage/extraction, or another artifact-action bottleneck. The Node deprecation warnings are not evidence of the cause. Measuring transfer/extraction separately, reducing the archive size, and budgeting artifact setup independently of test execution would help isolate and mitigate this failure.
Suggested updated title:
CI flake: Rust shard exceeds 10m limit downloading rust-tests-linux archiveDuplicate analysis
Searched open and closed public issues using
rust-tests-linux,Download Rust test archive, and broadartifact timeout,download cancelled, andmaximum execution timeterms; inspected relevant Test flakes tickets and closed-ticket timelines.Leaving open: #6330 is not an authorized automatic duplicate-closure target.