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).
2 files changed, 2 insertions(+), 2 deletions(-)
ci
ci/x86_64-windows-debug.ps1+1-1
| ... | ... | @@ -60,7 +60,7 @@ Write-Output "Main test suite..." |
| 60 | 60 | -Dskip-non-native ` |
| 61 | 61 | -Dskip-release ` |
| 62 | 62 | -Denable-symlinks-windows ` |
| 63 | | --test-timeout 10m |
| 63 | --test-timeout 30m |
| 64 | 64 | CheckLastExitCode |
| 65 | 65 | |
| 66 | 66 | Write-Output "Build x86_64-windows-msvc behavior tests using the C backend..." |
ci/x86_64-windows-release.ps1+1-1
| ... | ... | @@ -59,7 +59,7 @@ Write-Output "Main test suite..." |
| 59 | 59 | -Dstatic-llvm ` |
| 60 | 60 | -Dskip-non-native ` |
| 61 | 61 | -Denable-symlinks-windows ` |
| 62 | | --test-timeout 10m |
| 62 | --test-timeout 30m |
| 63 | 63 | CheckLastExitCode |
| 64 | 64 | |
| 65 | 65 | # Ensure that stage3 and stage4 are byte-for-byte identical. |
Matthew Lugg <mlugg@mlugg.co.uk> 2025-10-16 12:41:55+01:00
Commit is signed but in an unrecognized format.