CI flake: unity-testsuite

[clockwork-labs-bot]

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

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/33130353428/job/98719179264 (unity-testsuite, attempt 1 -> 2)

Timeout detection:

• none

Context:

• none

[clockwork-labs-bot]

Exact-attempt diagnosis:

The linked job is public CI run 33130353428, job 98719179264, unity-testsuite, attempt 1. The job API also reports run_attempt: 1, matching the ticket's attempt 1 -> 2 rerun. This was PR #5793 (tien/feat/egress-mcp-root), head SHA adc4f697fecff252d00b92e9a10f292fe61cb945, on runner ghr-github-self-hosted-ubuntu-14900k-01-spacetimedb-14-25daa6ad.

Setup completed before the failure: checkout, Unity Library restore, .NET restore/package override, Rust/cache setup, build artifact download, Unity client binding generation, Unity meta-file check, local SpacetimeDB startup, and publishing the unity-tests module. The only failed step was Run Unity tests.

Inside game-ci/unity-test-runner@v4, Unity 2022.3.32f1 first completed activation successfully and logged Activation successful. When the action then launched the playmode test editor, the editor connected to the licensing client but no active headless entitlement was available:

[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
##[error]The process '/usr/bin/docker' failed with exit code 1

Cleanup then logged Seat id doesn't belong to user while trying to return the entitlement license. Root cause for this exact attempt looks like Unity/GameCI license entitlement state becoming invalid between activation and playmode startup. This is CI licensing infrastructure, not a SpacetimeDB Unity test assertion failure.

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

Duplicate search:

Top duplicate candidate: #5581, open, same unity-testsuite failure mechanism with License is not active (com.unity.editor.headless) / No valid Unity Editor license found before playmode results are produced.

Other public Test Flakes tickets in the same family: #5626, #5721, and #5585 are closed repeats of the Unity headless-license-not-active signature. Related but less exact tickets include #5302 for Unity access-token/update-license failures and #5639 / #5796 for Unity playmode SIGSEGV / exit 139 cases where licensing noise appears in the log but the visible terminal failure is a crash, not inactive headless entitlement.

Leaving this ticket open because #5581 is not in the configured auto-close duplicate target list for this followup.