On 17/6/22 21:02, Emil Velikov wrote:
On Wed, 15 Jun 2022 at 00:47, Allan McRae <[email protected]> wrote:
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.
Can't we install the glibc-debug package or does valgrind insist on
the debuginfod service? The install will require enabling the
core-debug repo, which is annoying but doable.
IMHO keeping the CI green is a number one priority. Don't see a reason
to block your patch, even if my idea seems reasonable.
Forgot to send the updated patch. The following command is now added to
the valgrind section:
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
Not idea, but works!
