From d1e95c4e540283ff5d2a108459582ce2fa05c6ff Mon Sep 17 00:00:00 2001 From: Allan McRae Date: Thu, 9 Jun 2022 08:58:27 +1000 Subject: [PATCH] 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 --- .gitlab-ci.yml | 1 + 1 file changed, 1 insertion(+) 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