CI flake: unity-testsuite

[clockwork-labs-bot]

Detected by CI Gremlin after a failed merge-queue run succeeded in a later merge-queue run without a new PR head commit.

Tests:

• unity-testsuite

Error:
[Licensing::Module] Error: License is not active (com.unity.editor.headless). HasEntitlements will fail.
Pro License: NO

Failed job runs:

• https://github.com/clockworklabs/SpacetimeDB/actions/runs/30009394931/job/89214820499 (unity-testsuite, attempt merge queue run 30009394931 -> merge queue run 30089790505)

Timeout detection:

• none

Context:

• Merge queue PR: Fix release flow #5579
• PR head SHA: 42a3aee
• Later successful run: https://github.com/clockworklabs/SpacetimeDB/actions/runs/30089790505

[clockwork-labs-bot]

Diagnosis for the exact linked job/attempt: run 30009394931, job 89214820499, unity-testsuite, attempt 1.

GitHub's job API reports the linked job as run_attempt: 1, matching the merge-queue failure in the ticket. The workflow event was merge_group on gh-readonly-queue/master/pr-5579-42a3aeea0f1e7d5a102d69f617bd15d515cf696e, with merge-group head SHA 24ea67d9897ca479c01fc30ed1098cad4b423061; the ticket records PR #5579 head SHA 42a3aeea0f1e7d5a102d69f617bd15d515cf696e.

This was not a SpacetimeDB test assertion failure. The job completed setup successfully: checkout, .NET restore, Rust toolchain/cache, V8 output check, local CLI install, Unity client binding generation, Unity SDK DLL hydration, Unity meta check, SpacetimeDB startup, and publishing the unity-tests module all passed. The only failed step was Run Unity tests.

The Unity runner started playmode testing with Unity 2022.3.32f1, connected to the licensing client, then failed before producing playmode-results.xml:

[Licensing::Module] Error: Access token is unavailable; failed to update
[Licensing::Client] Successfully updated license
[Licensing::Client] Successfully resolved entitlements
[Licensing::Module] Error: License is not active (com.unity.editor.headless). HasEntitlements will fail.
Pro License: NO
No valid Unity Editor license found. Please activate your license.
Unexpected exit code 1
cat: /github/workspace/artifacts/playmode-results.xml: No such file or directory

During cleanup / license return, Unity then logged:

[Licensing::Client] Error: Code 400006 while processing request (status: Bad request: Seat id doesn't belong to user)
[Licensing::Module] Error: Failed to return entitlement license
[Licensing::Module] Error: Serial number unavailable for ULF return; skipping operation
##[error]The process '/usr/bin/docker' failed with exit code 1

Root cause visible in this exact attempt: Unity headless license activation/entitlement state inside the game-ci/unity-test-runner@v4 container was invalid. The test runner could not obtain an active com.unity.editor.headless license, so no Unity playmode tests actually ran. This is an infrastructure/licensing flake, not a product test failure.

Suggested updated title: CI flake: unity-testsuite Unity headless license not active

Duplicate check in the Test Flakes project:

• Top duplicate candidate: CI flake: unity-testsuite #5581. It is an open exact match for unity-testsuite failing before playmode results because Unity reports License is not active (com.unity.editor.headless) / No valid Unity Editor license found.
• Related but not exact: CI flake: unity-testsuite - access token is unavailable #5302 is the older open Unity licensing/access-token tracker; CI flake: unity-testsuite #5408, CI flake: unity-testsuite #5409, and CI flake: unity-testsuite #5304 are closed repeats of the access-token/update-license signature. Those are adjacent Unity licensing failures, but this ticket's distinctive failure is the inactive headless entitlement.
• Not duplicates: CI flake: unity-testsuite #5515 is a Unity job timeout during cold Library rebuild/import, and CI flake: unity-testsuite - 502 pulling Unity editor #5282 is a Docker Hub 502 while pulling the Unity editor image.

I would treat #5581 as the canonical duplicate for this signature.