From dd4bea7fd8c1e09ce6d8a66323b30c82e4a568c1 Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Thu, 13 Nov 2025 17:48:09 +1300 Subject: [PATCH v2 1/5] ci: Use Visual Studio 2022, for . XXX No opinion on when we could require this as a baseline. We only just pulled the trigger on Visual Studio 2019 which added lots of C11, but lacked . (Thanks to Bilal for getting this onto the CI image!) --- .cirrus.tasks.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.cirrus.tasks.yml b/.cirrus.tasks.yml index 2fe9671f3dc..266ce99e7db 100644 --- a/.cirrus.tasks.yml +++ b/.cirrus.tasks.yml @@ -767,11 +767,12 @@ WINDOWS_ENVIRONMENT_BASE: &WINDOWS_ENVIRONMENT_BASE task: - name: Windows - Server 2022, VS 2019 - Meson & ninja + name: Windows - Server 2022, VS 2022 - Meson & ninja << : *WINDOWS_ENVIRONMENT_BASE env: TEST_JOBS: 8 # wild guess, data based value welcome + PATH: C:\VS_2022\VC\Auxiliary\Build;${PATH} # Cirrus defaults to SetErrorMode(SEM_NOGPFAULTERRORBOX | ...). That # prevents crash reporting from working unless binaries do SetErrorMode() -- 2.50.1 (Apple Git-155)