Commit 3d0009b9c6

Matthew Lugg <mlugg@mlugg.co.uk>
2025-10-16 13:41:55
ci: bump test timeouts to stupid numbers on Windows
Unfortunately, Windows' scheduler means that test timeouts get hit very easily, because it seems the system can refuse to schedule a waiting process for *upwards of 10 minutes*. We should look for a better solution for this problem going forwards, but for now, just give Windows a very high test timeout. The 30 minute timeout set here is around the duration of a *full CI run* on Windows, so it should be impossible to hit normally, but it means that if a test gets stuck we'll at least get told (eventually).
master
1 parent f4315a0
Changed files (2)
ci
x86_64-windows-debug.ps1
x86_64-windows-release.ps1
ci/x86_64-windows-debug.ps1
@@ -60,7 +60,7 @@ Write-Output "Main test suite..."
   -Dskip-non-native `
   -Dskip-release `
   -Denable-symlinks-windows `
-  --test-timeout 10m
+  --test-timeout 30m
 CheckLastExitCode
 
 Write-Output "Build x86_64-windows-msvc behavior tests using the C backend..."
ci/x86_64-windows-release.ps1
@@ -59,7 +59,7 @@ Write-Output "Main test suite..."
   -Dstatic-llvm `
   -Dskip-non-native `
   -Denable-symlinks-windows `
-  --test-timeout 10m
+  --test-timeout 30m
 CheckLastExitCode
 
 # Ensure that stage3 and stage4 are byte-for-byte identical.