From 42e810e2c193cdbf6b64584d33c6770ff1c8546b Mon Sep 17 00:00:00 2001 From: Philip Withnall Date: Thu, 8 Dec 2022 15:27:24 +0000 Subject: [PATCH] =?UTF-8?q?ci:=20Don=E2=80=99t=20fail=20if=20testlog-unsta?= =?UTF-8?q?ble=5Ftests.junit.xml=20doesn=E2=80=99t=20exist=20on=20MSVC?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit That file is created if running the `unstable_tests` suite succeeds. It can fail, though, leaving that log file nonexistent. There’s no point in failing the whole test run by bailing out if postprocessing the log file fails. Occasionally postprocessing can fail with a `FileNotFoundError`. Signed-off-by: Philip Withnall --- .gitlab-ci/test-msvc.bat | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitlab-ci/test-msvc.bat b/.gitlab-ci/test-msvc.bat index 1ad2e4a57..48b5668d5 100644 --- a/.gitlab-ci/test-msvc.bat +++ b/.gitlab-ci/test-msvc.bat @@ -22,7 +22,7 @@ meson test -C _build --timeout-multiplier %MESON_TEST_TIMEOUT_MULTIPLIER% --setu :: Workaround meson issue https://github.com/mesonbuild/meson/issues/9894 python -c "n = '_build/meson-logs/testlog.junit.xml'; c = open(n, 'rb').read().replace(b'\x1b', b''); open(n, 'wb').write(c)" || goto :error -python -c "n = '_build/meson-logs/testlog-unstable_tests.junit.xml'; c = open(n, 'rb').read().replace(b'\x1b', b''); open(n, 'wb').write(c)" || goto :error +python -c "n = '_build/meson-logs/testlog-unstable_tests.junit.xml'; c = open(n, 'rb').read().replace(b'\x1b', b''); open(n, 'wb').write(c)" :: FIXME: can we get code coverage support?