From 3d0009b9c621f6cd72ff9eea193a7094e0c2a700 Mon Sep 17 00:00:00 2001 From: Matthew Lugg Date: Thu, 16 Oct 2025 12:41:55 +0100 Subject: [PATCH] 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). --- ci/x86_64-windows-debug.ps1 | 2 +- ci/x86_64-windows-release.ps1 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/ci/x86_64-windows-debug.ps1 b/ci/x86_64-windows-debug.ps1 index 65828c093d..6cd28db466 100644 --- a/ci/x86_64-windows-debug.ps1 +++ b/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..." diff --git a/ci/x86_64-windows-release.ps1 b/ci/x86_64-windows-release.ps1 index 246d9a993c..f3cdd66f48 100644 --- a/ci/x86_64-windows-release.ps1 +++ b/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.