clockworklabs / clockworklabs/SpacetimeDB
CI flake: unity-testsuite CreatePlayerAndTestDecay logs Mass should have decayed
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.
Tests:
unity-testsuite
Error:
Test(s) Failed! Check 'Test Results' for details.
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/30665901224/job/91273717810 (unity-testsuite, attempt 1 -> 2)
Timeout detection:
- none
Context:
- none
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failed GitHub Actions job for the unity-testsuite and inspect Test Results for CreatePlayerAndTestDecay. Compare the failed attempt with its successful rerun, then trace the test's failure conditions. Done means the test no longer flakes in CI and the Mass decay expectation is consistently satisfied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, unity
- Domain
- ci-cd, game-dev, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100