Gitlab CI: run the tests through valgrind on the f28 box

We don't run it on all machines, valgrind fails right now on arch because of a
memleak in bash itself. To avoid having CI failures that aren't our fault,
only run on F28 because that's the one I'm tracking.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 38e6986..6fe98c9 100644 (file)
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -587,6 +587,16 @@ fedora:28@scan-build:
     - echo "Check scan-build results"
     - /bin/false
 
+fedora:28@valgrind:
+  <<: *fedora_28_template
+  variables:
+    FEDORA_VERSION: 28
+  script:
+   - rm -rf $MESON_BUILDDIR
+   - meson $MESON_BUILDDIR $MESON_PARAMS
+   - meson configure $MESON_BUILDDIR
+   - meson test -C "$MESON_BUILDDIR" --setup=valgrind
+
 #
 # Ubuntu
 #