From 21aaaf4a61fa4c219cf3d5b8760068c8930f405f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vladim=C3=ADr=20Vondru=C5=A1?= Date: Sun, 4 Dec 2022 20:51:23 +0100 Subject: [PATCH] package/ci: add a CTest timeout to Windows jobs. Because otherwise THE DAMN THING just waits endlessly for me to click the "Abort" button on AN ASSERT DIALOG BOX! ON A HEADLESS CI!! MICROSOFT!!! --- package/ci/appveyor-desktop-gles.bat | 8 +++++++- package/ci/appveyor-desktop-mingw.bat | 8 +++++++- package/ci/appveyor-desktop.bat | 8 +++++++- 3 files changed, 21 insertions(+), 3 deletions(-) diff --git a/package/ci/appveyor-desktop-gles.bat b/package/ci/appveyor-desktop-gles.bat index 876213dfd..4f7e577a8 100644 --- a/package/ci/appveyor-desktop-gles.bat +++ b/package/ci/appveyor-desktop-gles.bat @@ -63,7 +63,13 @@ cmake --build . || exit /b rem Test set CORRADE_TEST_COLOR=ON -ctest -V -E "GLTest|GLBenchmark" || exit /b +rem On Windows, if an assertion or other issue happens, A DIALOG WINDOWS POPS +rem UP FROM THE CONSOLE. And then, for fucks sake, IT WAITS ENDLESSLY FOR YOU +rem TO CLOSE IT!! Such behavior is utterly stupid in a non-interactive setting +rem such as on this very CI, so I'm setting a timeout to 60 seconds to avoid +rem the CI job being stuck for an hour if an assertion happens. CTest's default +rem timeout is somehow 10M seconds, which is as useful as nothing at all. +ctest -V -E "GLTest|GLBenchmark" --timeout 60 || exit /b rem Test install, after running the tests as for them it shouldn't be needed cmake --build . --target install || exit /b diff --git a/package/ci/appveyor-desktop-mingw.bat b/package/ci/appveyor-desktop-mingw.bat index 445fb1782..0a1eae4ca 100644 --- a/package/ci/appveyor-desktop-mingw.bat +++ b/package/ci/appveyor-desktop-mingw.bat @@ -60,7 +60,13 @@ cmake --build . || exit /b rem Test set CORRADE_TEST_COLOR=ON -ctest -V -E "GLTest|GLBenchmark|VkTest" || exit /b +rem On Windows, if an assertion or other issue happens, A DIALOG WINDOWS POPS +rem UP FROM THE CONSOLE. And then, for fucks sake, IT WAITS ENDLESSLY FOR YOU +rem TO CLOSE IT!! Such behavior is utterly stupid in a non-interactive setting +rem such as on this very CI, so I'm setting a timeout to 60 seconds to avoid +rem the CI job being stuck for an hour if an assertion happens. CTest's default +rem timeout is somehow 10M seconds, which is as useful as nothing at all. +ctest -V -E "GLTest|GLBenchmark|VkTest" --timeout 60 || exit /b rem Test install, after running the tests as for them it shouldn't be needed cmake --build . --target install || exit /b diff --git a/package/ci/appveyor-desktop.bat b/package/ci/appveyor-desktop.bat index 8da958352..56d62f670 100644 --- a/package/ci/appveyor-desktop.bat +++ b/package/ci/appveyor-desktop.bat @@ -71,7 +71,13 @@ cmake --build . || exit /b rem Test set CORRADE_TEST_COLOR=ON -ctest -V -E "GLTest|GLBenchmark|VkTest" || exit /b +rem On Windows, if an assertion or other issue happens, A DIALOG WINDOWS POPS +rem UP FROM THE CONSOLE. And then, for fucks sake, IT WAITS ENDLESSLY FOR YOU +rem TO CLOSE IT!! Such behavior is utterly stupid in a non-interactive setting +rem such as on this very CI, so I'm setting a timeout to 60 seconds to avoid +rem the CI job being stuck for an hour if an assertion happens. CTest's default +rem timeout is somehow 10M seconds, which is as useful as nothing at all. +ctest -V -E "GLTest|GLBenchmark|VkTest" --timeout 60 || exit /b rem Test install, after running the tests as for them it shouldn't be needed cmake --build . --target install || exit /b