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/40404334163/job/121875253936 (Test Suite, attempt 1 -> 2)
Timeout detection:
- none
Context:
- none
Metadata
Metadata
Assignees
Labels
No labels
Activity
clockwork-labs-bot commentedon Oct 26, 2026
Symptoms and root cause
Observed in run 40404334163, Test Suite job 121875253936, attempt 1: the aggregate gate exits 1 at
test "${RUST_RESULT}" = successbecauseRUST_RESULT=cancelled. The other six component results aresuccess; orphan-process cleanup is downstream, not the cause.Followed this to Test Suite - Rust (4/4), job 121865985762, same run, attempt 1:
Download Rust test archiveselectsrust-tests-linux, artifact 12691367790, 5,598,897,139 bytes.The operation was canceled.at 21:55:54.970 UTC, about 9m56s later.The job has exceeded the maximum execution time of 10m0s. The download step is cancelled andRun Rust test partitionis skipped.The primary observable issue is Rust archive handling exhausting the shard's job budget; this ticket records its aggregate-gate propagation, not a separate test failure or cancellation-only incident. Network, storage/extraction, or an artifact-action bottleneck remain hypotheses; these logs do not establish which caused the slow handling.
Duplicate selection
Searched open issues only using
rust-tests-linux, archive/timeout terms, and Rust job names, and inspected matching reports. Selected open root: #6330, covering Rust test archive transfer exhausting the shard budget. It has the same specific artifact-download timeout before tests start; the larger archive and aggregate-job manifestation do not make this a different issue.Canonical selection was checked against actual duplicate relationships visible on the open candidates: #6330 has 8 distinct incoming duplicate sources and no subsequent unmarks; matching open #6355, #6356, #6371, and #6372 each have 0. Ordinary cross-references were not counted. #6388 is the upstream incident ticket for this same run, not a competing established root. No closed tickets were searched or inspected to reconstruct history.
Proposed operations
DRY RUN — proposal only: close this new ticket as a duplicate of #6330, using GitHub's canonical duplicate relationship. The root was rechecked open immediately before publishing. No title/team operations are proposed for a duplicate, and no triage fields, state, or duplicate relationships have been changed. Existing/root tickets are not modified.