Godot Blackholio completion#5030
Conversation
d9a4371 to
0c10ba6
Compare
af82eb5 to
c2f7cb9
Compare
c2f7cb9 to
562bb5d
Compare
562bb5d to
32fae12
Compare
| <PackageOutputPath>bin~/$(Configuration)/</PackageOutputPath> | ||
| <BaseIntermediateOutputPath>obj~/godot/</BaseIntermediateOutputPath> | ||
| <IntermediateOutputPath>obj~/godot/$(Configuration)/$(TargetFramework)/</IntermediateOutputPath> | ||
| <UseLocalBsatnRuntime Condition="'$(UseLocalBsatnRuntime)' == ''">false</UseLocalBsatnRuntime> |
There was a problem hiding this comment.
I think we determined that this didn't actually fix the flakiness, is that right?
| permissions: | ||
| contents: read | ||
| runs-on: spacetimedb-new-runner-2 | ||
| timeout-minutes: 30 |
There was a problem hiding this comment.
how long does a typical successful run take?
There was a problem hiding this comment.
FWIW we usually only add this when we've had issues with a job hanging
| # Run cheap .NET setup first. If that fails, no need to run expensive Godot tests. | ||
|
|
There was a problem hiding this comment.
I don't think this comment makes any sense? the dotnet setup is required for tests, isn't it?
| # Run cheap .NET setup first. If that fails, no need to run expensive Godot tests. |
|
|
||
| - name: Build Godot .NET project | ||
| working-directory: demo/Blackholio/client-godot | ||
| run: dotnet build --no-restore -v normal blackholio.csproj |
| - name: Publish godot-tests module to SpacetimeDB | ||
| working-directory: demo/Blackholio/server-rust | ||
| run: | | ||
| spacetime logout && spacetime login --server-issued-login local |
There was a problem hiding this comment.
nit: I think the logout part is redundant now. 1) because it's in an ephemeral runner and 2) because we recently made spacetime login automatically do the logout if needed
| spacetime logout && spacetime login --server-issued-login local | |
| spacetime login --server-issued-login local |
bfops
left a comment
There was a problem hiding this comment.
The CI part looks pretty good to me, minus a few small comments. It looks like the CI is failing, though.
Description of Changes
API and ABI breaking changes
Expected complexity level and risk
Testing