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
Exact failed Rust shard job: run 44078291964, job 134070533410, attempt 2. Download Rust test archive spent 9m53s handling the 5,555,285,561-byterust-tests-linux artifact, until the check-run annotation reported The job has exceeded the maximum execution time of 10m0s. Download started at 13:24:24 UTC; no completion message appeared before cancellation at 13:34:16. Run Rust test partition was skipped. The transfer/handling exhausted the shared job budget; the logs do not distinguish a network stall, storage/extraction bottleneck, or other artifact-action slowdown. This is a genuine timeout, not cancellation-only. Attempt 3, job 134131580581, downloaded the same artifact and passed 424/424 tests.
Duplicate selection
Searched all 106 open Test flakes project issues across repositories, plus organization-wide open archive/artifact/timeout/job-budget searches. Selected #6330: the same specific symptom—Rust archive transfer/handling consumes the shard job budget, before tests start. Its established consolidation and 44 distinct incoming canonical duplicate sources (before this invocation) support it as the root. Artifact listing connection reset (#6535), checksum mismatch (#6369), truncated build-support artifact (#5949), and every-component-skipped aggregate (#5930) have different diagnostics absent here. Only open candidate tickets were investigated; no existing/root ticket was modified.
Activity
clockwork-labs-bot commentedon Nov 17, 2026
Symptoms and root cause
Exact failed Rust shard job: run
44078291964, job134070533410, attempt 2.Download Rust test archivespent 9m53s handling the 5,555,285,561-byterust-tests-linuxartifact, until the check-run annotation reported The job has exceeded the maximum execution time of 10m0s. Download started at 13:24:24 UTC; no completion message appeared before cancellation at 13:34:16.Run Rust test partitionwas skipped. The transfer/handling exhausted the shared job budget; the logs do not distinguish a network stall, storage/extraction bottleneck, or other artifact-action slowdown. This is a genuine timeout, not cancellation-only. Attempt 3, job134131580581, downloaded the same artifact and passed 424/424 tests.Duplicate selection
Searched all 106 open Test flakes project issues across repositories, plus organization-wide open archive/artifact/timeout/job-budget searches. Selected #6330: the same specific symptom—Rust archive transfer/handling consumes the shard job budget, before tests start. Its established consolidation and 44 distinct incoming canonical duplicate sources (before this invocation) support it as the root. Artifact listing connection reset (#6535), checksum mismatch (#6369), truncated build-support artifact (#5949), and every-component-skipped aggregate (#5930) have different diagnostics absent here. Only open candidate tickets were investigated; no existing/root ticket was modified.
Proposed operations
duplicateOfCI flake - Rust test archive transfer exhausts shard job budget #6330. No title/team changes or root edits. All other triage operations remain subject to DRY RUN.