CI flake: godot-testsuite

[clockwork-labs-bot]

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

Tests:

• godot-testsuite

Error:
Process completed with exit code 139.
sccache --show-stats

Failed job runs:

• https://github.com/clockworklabs/SpacetimeDB/actions/runs/34492782945/job/102924923711 (godot-testsuite, attempt 1 -> 2)

Timeout detection:

• none

Context:

• none

[clockwork-labs-bot]

Diagnosis for the exact linked job/attempt: public run 34492782945, job 102924923711, godot-testsuite, attempt 1. This was PR CI for branch jlarabie/shard-test-suite, head SHA 448902e3aa5dabd679fdf2beb9a07e64198136a8, using refs/pull/5854/merge.

Setup, C# package build, Godot install, Godot solution build, SpacetimeDB startup, login, and Blackholio module publish all succeeded. The failure happened in the final playmode command:

godot --headless --scene res://tests/GodotPlayModeTests.tscn

All four Godot test cases logged PASS first: SimpleConnectionTest, CreatePlayerAndTestDecay, OneOffQueryTest, and ReconnectionViaReloadingScene. Immediately afterward, Godot logged several Leaked unsafe reference to object errors during Mono finalization, then crashed:

handle_crash: Program crashed with signal 11
Segmentation fault (core dumped) godot --headless --scene res://tests/GodotPlayModeTests.tscn
Process completed with exit code 139.

Root cause visible in this exact attempt: the Godot 4.6.2 Mono process segfaulted during/after teardown of the headless playmode scene, after the SpacetimeDB-facing test assertions had already passed. This is a Godot runtime/Mono teardown crash, not a SpacetimeDB server startup failure, module publish failure, C# package build failure, or failed Godot test assertion.

Suggested updated title: CI flake: godot-testsuite Godot headless playmode crashes with signal 11 after tests pass

Duplicate analysis: I searched public Test Flakes/issues for exact and broad signatures including Program crashed with signal 11, Leaked unsafe reference to object, GodotPlayModeTests, exit code 139 Godot, and signal 11 Godot, plus an org-wide fallback for the Godot signal-11 headline. I did not find a close public duplicate. Similar public tickets may exist for Unity/Godot licensing or setup failures, but none are close enough to mark this as a duplicate of this teardown segfault.

Top duplicate candidate: none close enough; leaving this open.