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 1.
Cleaning up orphan processes

Failed job runs:

• https://github.com/clockworklabs/SpacetimeDB/actions/runs/34625491168/job/103349993590 (Test Suite, attempt 1 -> 3)

Timeout detection:

• none

Context:

• none

[clockwork-labs-bot]

Diagnosis for the exact linked job/attempt: CI run 34625491168, job 103349993590, Test Suite, attempt 1.

This was PR #5863 (jlarabie/shard-test-suite-2) at head 9fb2b86ec3309bafd33afe260d90922677c1f190, running on ghr-github-self-hosted-ubuntu-14900k-07-spacetimedb-14-81be9058. The job completed in about two seconds and did not execute a test shard. It only ran the Check component results step.

The exact failure was the aggregate check comparing component-result environment variables to success:

test "${RUST_BUILD_RESULT}" = success
test "${RUST_RESULT}" = success
test "${RUST_SERIAL_RESULT}" = success
test "${CSHARP_RESULT}" = success
test "${CPP_RESULT}" = success
test "${SDK_NATIVE_RESULT}" = success
test "${SDK_BROWSER_RESULT}" = success

env:
  RUST_RESULT: skipped
  RUST_BUILD_RESULT: skipped
  RUST_SERIAL_RESULT: skipped
  CSHARP_RESULT: skipped
  CPP_RESULT: skipped
  SDK_NATIVE_RESULT: skipped
  SDK_BROWSER_RESULT: skipped

Process completed with exit code 1.

Root cause visible in this exact attempt: this ticket is for a synthetic aggregate Test Suite job, not a failing test. The aggregate job failed because all component-result outputs were skipped, so the first test skipped = success check failed. The exact job log does not contain a product failure or a failing test name.

Suggested updated title: CI flake: Test Suite aggregate failed because component results were skipped

Duplicate analysis:

• Top duplicate candidate: none close enough to mark as a duplicate.
• Similar ticket in the same run: CI flake: Lints #5929 is the substantive failed Lints job in attempt 1, but it is a different workflow job and a different failure mechanism, so I would not mark this aggregate ticket as a duplicate of it.
• Public duplicate searches for Check component results, RUST_RESULT skipped, RUST_BUILD_RESULT skipped, and the generic Process completed with exit code 1 aggregate signature did not find an older public Test Flakes ticket with this same mechanism.

Top duplicate candidate: none; leaving this ticket open.