aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAllan McRae <allan@archlinux.org>2022-06-09 08:58:27 +1000
committerAllan McRae <allan@archlinux.org>2022-06-16 09:00:18 +1000
commitd1e95c4e540283ff5d2a108459582ce2fa05c6ff (patch)
tree27fc4fa351c385dd8e21858feb82653f4cea4d65
parent84dc662d6527be261cf2288d5af2dd7f7e4207dd (diff)
Gitlab CI: Install glibc-debug valgrind test
Currently our gitlab CI is failing due to valgrind breakage. With Arch stripping glibc, valgrind now requires debuginfod to be active. However the gitlab CI system combined without our testsuite does not retrieve these symbols, even when the appropriate environmental variable is set. Work around this by installing the glibc-debug package directly using a slight kludge... All blame for this approach is assigned to foutrelis! Signed-off-by: Allan McRae <allan@archlinux.org>
-rw-r--r--.gitlab-ci.yml1
1 files changed, 1 insertions, 0 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 186ad3dc..528a5e35 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -50,6 +50,7 @@ arch-valgrind:
extends: .arch-test
script:
- pacman -Syu --needed --noconfirm valgrind
+ - pacman -U --noconfirm https://geo.mirror.pkgbuild.com/core-debug/os/x86_64/glibc-debug-$(pacman -S --print-format %v glibc)-x86_64.pkg.tar.zst
- meson build
- ninja -C build
- PACTEST_VALGRIND=1 fakechroot meson test -C build