Add CI tests with -fsanitize=address,undefined. This is a bit complicated since our tests run through Python FFI and we have to
link with -shared-libasan
preload the ASan runtime
disable LeakSanitizer because of false positives from Python
Use a single matrix on POSIX with four human readable labels:
posix (os, compiler, build_type, sanitizers)
Disable gcc on macOS which is just an alias for clang.
Remove the valgrind leakcheck test. This should be covered now by testing with LeakSanitizer on static builds, including tests like spectest_executable. The full test suite is only available to shared library builds which have to run without leak checks for now.
Add CI tests with -fsanitize=address,undefined. This is a bit complicated since our tests run through Python FFI and we have to
Use a single matrix on POSIX with four human readable labels:
Disable gcc on macOS which is just an alias for clang.
Remove the valgrind leakcheck test. This should be covered now by testing with LeakSanitizer on static builds, including tests like spectest_executable. The full test suite is only available to shared library builds which have to run without leak checks for now.
Also rework the Windows matrix.