CI flake: Test Suite

[clockwork-labs-bot]

Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.

Tests:

• Test Suite

Error:
Process completed with exit code 100.
Post job cleanup.

Failed job runs:

• https://github.com/clockworklabs/SpacetimeDB/actions/runs/28347511239/job/83974173214 (Test Suite, attempt 1 -> 2)

Context:

• none

[clockwork-labs-bot]

Diagnosis for the linked job attempt:

The linked public Test Suite job failed before Rust tests ran. It checked out PR #5455 merge ref 1e27dc77c5fec608d5936b1c61e96ab6cb69db33, completed dependency setup, then failed in the Emscripten setup step:

sudo apt-get update
sudo apt-get install -y cmake

apt-get update completed, but apt-get install -y cmake exited 100 because the runner had unattended upgrades holding the dpkg frontend lock:

E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 1995 (unattended-upgr)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

Root cause for this exact attempt: runner OS package-manager contention from unattended-upgr, not a SpacetimeDB test failure. The workflow does not wait/retry before apt install, so transient apt lock contention fails the job.

Suggested title:

CI flake: Test Suite apt install blocked by unattended-upgr dpkg lock

Duplicate check:

Likely duplicate:

• CI flake: Could not get lock /var/lib/dpkg/lock-frontend #5273: same Test Suite class and already titled for /var/lib/dpkg/lock-frontend.

Similar but not close enough:

• CI flake: Test Suite #5422 / CI flake: Test Suite #5257: generic Test Suite exit code 100 tickets; their issue bodies do not identify the dpkg lock signature.

Top duplicate candidate: #5273.