ci/linux: split normal testing from valgrind testing A test case failure usually also triggers valgrind leaks, sifting through those to find the actual test failure is painful. So let's separate the tests and run them separately. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
diff --git a/.github/workflows/linux.yml b/.github/workflows/linux.yml
index 5dede6d..d5f1d2e 100644
--- a/.github/workflows/linux.yml
+++ b/.github/workflows/linux.yml
@@ -37,4 +37,7 @@ jobs:
meson compile -C build
- name: Test
run:
+ meson test -C build --print-errorlogs --no-suite python-tests
+ - name: Test with valgrind
+ run:
meson test -C build --print-errorlogs --setup=valgrind --no-suite python-tests