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 does not retrieve these symbols, even when the appropriate environmental variable is set. If Arch is not appropriate for this test, we may want to switch to another distribution for valgrind. Signed-off-by: Allan McRae <allan@archlinux.org> --- This is a temporary patch to get CI running clean again. Still looking at how this can be fixed for Arch, otherwise I will switch the valgrind run to a distro with appropriate dependencies for valgrind to run. .gitlab-ci.yml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 186ad3dc..d9659746 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -46,13 +46,14 @@ arch-clang: - ninja -C build - fakechroot meson test -C build -arch-valgrind: - extends: .arch-test - script: - - pacman -Syu --needed --noconfirm valgrind - - meson build - - ninja -C build - - PACTEST_VALGRIND=1 fakechroot meson test -C build +# Fails due to lack of debug symbols in libc.so.6 and debuginfod not working +#arch-valgrind: +# extends: .arch-test +# script: +# - pacman -Syu --needed --noconfirm valgrind +# - meson build +# - ninja -C build +# - PACTEST_VALGRIND=1 fakechroot meson test -C build arch-nettle: extends: .arch-test -- 2.36.1