ci: Halt on sanitizer errors

The undefined behaviour sanitizer (UBSAN) defaults to merely printing an
error message if it detects undefined behaviour. These error messages often
end up in captured output and do not fail the tests, effectively hiding
the warning. Make the test cases fail to make the issues visible.

Signed-off-by: Tim Wiederhake <twiederh@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 3cb6ff5e6b262ab4970d5e38b71d4e269826919c..4757139fa96c067e35a08dcf49ffbed4f2464cce 100644 (file)
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -89,6 +89,8 @@ stages:
     - meson build --werror -Ddocs=disabled -Db_lundef=false -Db_sanitize="$SANITIZER"
     - ninja -C build;
     - ninja -C build test;
+  variables:
+    UBSAN_OPTIONS: print_stacktrace=1:halt_on_error=1
 
 # Jobs that we delegate to Cirrus CI because they require an operating
 # system other than Linux. These jobs will only run if the required