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 1.
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more...

Failed job runs:

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

Timeout detection:

• none

Context:

• none

[clockwork-labs-bot]

Diagnosis for the exact linked job/attempt: run 33098824720, job 98612609226, godot-testsuite, attempt 1.

GitHub's job API reports the linked job as run_attempt: 1, matching the ticket's attempt 1 -> 2 rerun. The workflow was public CI for PR #5833 / branch rekhoff/bump-versions, head SHA 569ed377aa5d305bd78a03157746eac980d449fb; the checked-out merge commit in the job was 4433297980a8a8a9ad5e458146da21c89e7657b6.

Setup completed successfully: checkout, .NET restore/package override, Rust toolchain/cache restore, artifact download/extract, Godot SDK binding generation, Godot setup/restore/build, SpacetimeDB startup, and publishing the blackholio module all passed. The failing step was Run Godot tests.

The detector headline included the final wrapper exit and a Node 20/24 deprecation warning, but the real failure was the Godot playmode test assertion:

[GodotTests] FAIL CreatePlayerAndTestDecay: System.Exception: Mass should decay. start=139, end=141

SimpleConnectionTest passed before it, and OneOffQueryTest plus ReconnectionViaReloadingScene passed after it. Root cause visible in this exact attempt: the Blackholio Godot CreatePlayerAndTestDecay test observed the player mass increasing instead of decaying during the test window. This looks like the same product/test timing or simulation flake already seen in the Godot mass-decay test, not a runner setup issue; the Node deprecation warning is incidental.

Suggested updated title: CI flake: godot-testsuite CreatePlayerAndTestDecay Mass should decay

Duplicate check in the Test Flakes project:

• Top duplicate candidate: CI flake: godot-testsuite - Mass should decay #5341 (CI flake: godot-testsuite - Mass should decay). It is the same suite and same CreatePlayerAndTestDecay assertion, with Mass should decay. start=135, end=136.
• Related but not top duplicate: CI flake: unity-testsuite CreatePlayerAndTestDecay logs Mass should have decayed #5644 is the same broad Blackholio mass-decay behavior in unity-testsuite, but it has a different client suite and failure surface (PlayModeExampleTest.CreatePlayerAndTestDecay / Mass should have decayed).
• Not a duplicate: closed CI flake: godot-testsuite #5442 is also godot-testsuite, but its root cause was a Godot/MSBuild exit-139 during --build-solutions, not this test assertion.

Leaving this ticket open because the top duplicate candidate is #5341, which is not one of the configured auto-close canonical targets.