| author |  Matthew Lugg <mlugg@mlugg.co.uk> 2025-10-16 12:41:55+01:00 |
| committer | Matthew Lugg <mlugg@mlugg.co.uk> 2025-10-18 09:28:44+01:00 |
| log | 3d0009b9c621f6cd72ff9eea193a7094e0c2a700 |
| tree | 42725cf49f5eac55445679b198f0d62de2bbf4fe |
| parent | f4315a0a577b416bb8eee7ab41ab0ea6e6defd04 |
| signature |  Commit is signed but in an unrecognized format. |
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/x86_64-windows-debug.ps1+1-1
| ... | @@ -60,7 +60,7 @@ Write-Output "Main test suite..." | ... | @@ -60,7 +60,7 @@ Write-Output "Main test suite..." |
| 60 | -Dskip-non-native ` | 60 | -Dskip-non-native ` |
| 61 | -Dskip-release ` | 61 | -Dskip-release ` |
| 62 | -Denable-symlinks-windows ` | 62 | -Denable-symlinks-windows ` |
| 63 | --test-timeout 10m | 63 | --test-timeout 30m |
| 64 | CheckLastExitCode | 64 | CheckLastExitCode |
| 65 | 65 | ||
| 66 | Write-Output "Build x86_64-windows-msvc behavior tests using the C backend..." | 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,7 +59,7 @@ Write-Output "Main test suite..." |
| 59 | -Dstatic-llvm ` | 59 | -Dstatic-llvm ` |
| 60 | -Dskip-non-native ` | 60 | -Dskip-non-native ` |
| 61 | -Denable-symlinks-windows ` | 61 | -Denable-symlinks-windows ` |
| 62 | --test-timeout 10m | 62 | --test-timeout 30m |
| 63 | CheckLastExitCode | 63 | CheckLastExitCode |
| 64 | 64 | ||
| 65 | # Ensure that stage3 and stage4 are byte-for-byte identical. | 65 | # Ensure that stage3 and stage4 are byte-for-byte identical. |