summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2020-02-21 10:37:56 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2020-02-24 01:53:21 +0000
commitdafb68f306b62ac483faf3b4c2ecb9cb021bc1b5 (patch)
tree1fe0c6a8a963100da31964fb9a7f9637d247ca02
parent20cf83789df6563828f16fc938ccf05437d366c2 (diff)
downloadlibinput-dafb68f306b62ac483faf3b4c2ecb9cb021bc1b5.tar.gz
gitlab CI: don't run meson test on the scan-build job
Unfortunate side-effect of this: scan-build would store the logs in the build dir, only for them to be immediately wiped by meson test. And that never generated the scan-build warnings. So this job was complaining about (minor) issues for a while, they just never made it to the GUI as CI failures. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-rw-r--r--.gitlab-ci.yml1
-rw-r--r--.gitlab-ci/gitlab-ci.tmpl1
2 files changed, 2 insertions, 0 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 259728bd..d0562998 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -655,6 +655,7 @@ scan-build@fedora:30:
- .fedora-build@template
variables:
NINJA_ARGS: scan-build
+ MESON_TEST_ARGS: ''
before_script:
- dnf install -y clang-analyzer findutils
after_script:
diff --git a/.gitlab-ci/gitlab-ci.tmpl b/.gitlab-ci/gitlab-ci.tmpl
index daa5dd5f..a744eb53 100644
--- a/.gitlab-ci/gitlab-ci.tmpl
+++ b/.gitlab-ci/gitlab-ci.tmpl
@@ -483,6 +483,7 @@ scan-build@fedora:30:
- .fedora-build@template
variables:
NINJA_ARGS: scan-build
+ MESON_TEST_ARGS: ''
before_script:
- dnf install -y clang-analyzer findutils
after_script: