Closed as duplicate
Description
Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.
Tests:
Test Suite
Error:
Process completed with exit code 1.
Cleaning up orphan processes
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/44078291964/job/134076380717 (Test Suite, attempt 2 -> 3)
Timeout detection:
- none
Context:
- none
Metadata
Metadata
Assignees
Labels
No labels
Activity
clockwork-labs-bot commentedon Nov 17, 2026
Symptoms and root cause
Exact failed aggregate job: run
44078291964, job134076380717, attempt 2.Check component resultsexits 1 solely becauseRUST_RESULT: cancelled; the other six component results aresuccess. Following that dependency to Rust shard job134070533410finds the ten-minute job timeout while downloading/handling the 5,555,285,561-byte Rust test archive for 9m53s; its test step never ran. This aggregate is downstream of that substantive timeout, not cancellation-only or a separate test failure. The artifact-action bottleneck is unproven. Attempt 3 passes Rust shard job134131580581(424/424 tests) and aggregate job134135480748.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.