Remove use of DDC during CI tests

[JasonAtClockwork]

Description of Changes

Removes the use of the Derived Data Cache during CI, will in

API and ABI breaking changes

None

Expected complexity level and risk

1 - Small change for CI

Testing

• Re-ran tests on both Linux + Windows with the change

[bfops]

Removes the use of the Derived Data Cache during CI, will in

?

[bfops]

Can you add some explanation (maybe inline comments) about what impact these settings make?

[JasonAtClockwork]

Can you add some explanation (maybe inline comments) about what impact these settings make?

Of course! I've added to the latest commit, let me know if the write up makes sense or if it needs more detail!

[bfops]

It looks like we're still getting SIGSEGV sometimes, but if you feel confident that this will decrease the frequency, I'm all for it.

thread 'unreal_insert_vec' panicked at crates/testing/src/sdk.rs:142:9:
(running): Error running "\"/home/ue4/UnrealEngine/Engine/Binaries/Linux/UnrealEditor\" \"/__w/SpacetimeDB/SpacetimeDB/sdks/unreal/tests/TestClient/TestClient.uproject\" -NullRHI -Unattended -NoSound -nop4 -NoSplash -NoZen -ddc=InstalledNoZenLocalFallback -ExecCmds=\"Automation RunTests SpacetimeDB.TestClient.InsertVecTest; Quit\"": exited with non-zero exit status signal: 11 (SIGSEGV) (core dumped). Output:
setrlimit() failed with error 22 (Invalid argument)
- Max per-process value allowed is 0 (we wanted infinity).

(https://github.com/clockworklabs/SpacetimeDB/actions/runs/18387938924/job/52727623047)

[JasonAtClockwork]

It looks like we're still getting SIGSEGV sometimes, but if you feel confident that this will decrease the frequency, I'm all for it.

thread 'unreal_insert_vec' panicked at crates/testing/src/sdk.rs:142:9:
(running): Error running "\"/home/ue4/UnrealEngine/Engine/Binaries/Linux/UnrealEditor\" \"/__w/SpacetimeDB/SpacetimeDB/sdks/unreal/tests/TestClient/TestClient.uproject\" -NullRHI -Unattended -NoSound -nop4 -NoSplash -NoZen -ddc=InstalledNoZenLocalFallback -ExecCmds=\"Automation RunTests SpacetimeDB.TestClient.InsertVecTest; Quit\"": exited with non-zero exit status signal: 11 (SIGSEGV) (core dumped). Output:
setrlimit() failed with error 22 (Invalid argument)
- Max per-process value allowed is 0 (we wanted infinity).

(https://github.com/clockworklabs/SpacetimeDB/actions/runs/18387938924/job/52727623047)

Oh that actually is a different error, setrlimit() is attempting to get some sort of resource increased but wasn't able. I'd guess memory would be a culprit here but I'm not 100% certain. I'll run some more tests on Linux and see if IO or Memory are higher than I expect.

[bfops]

It looks like we're still getting SIGSEGV sometimes, but if you feel confident that this will decrease the frequency, I'm all for it.

thread 'unreal_insert_vec' panicked at crates/testing/src/sdk.rs:142:9:
(running): Error running "\"/home/ue4/UnrealEngine/Engine/Binaries/Linux/UnrealEditor\" \"/__w/SpacetimeDB/SpacetimeDB/sdks/unreal/tests/TestClient/TestClient.uproject\" -NullRHI -Unattended -NoSound -nop4 -NoSplash -NoZen -ddc=InstalledNoZenLocalFallback -ExecCmds=\"Automation RunTests SpacetimeDB.TestClient.InsertVecTest; Quit\"": exited with non-zero exit status signal: 11 (SIGSEGV) (core dumped). Output:
setrlimit() failed with error 22 (Invalid argument)
- Max per-process value allowed is 0 (we wanted infinity).

(https://github.com/clockworklabs/SpacetimeDB/actions/runs/18387938924/job/52727623047)

Oh that actually is a different error, setrlimit() is attempting to get some sort of resource increased but wasn't able. I'd guess memory would be a culprit here but I'm not 100% certain. I'll run some more tests on Linux and see if IO or Memory are higher than I expect.

Okay perfect, then it sounds like this PR is still at least an improvement. I'll approve as-is!

[bfops]

It sounds like this addresses at least one source of errors, so let's merge it and keep iterating!