Hi Ryan (CC Andreas the s390x valgrind maintainer) On Fri, 2023-06-16 at 16:16 +0000, builder--- via Elfutils-devel wrote: > A new failure has been detected on builder elfutils-fedora-s390x while > building elfutils. > > Full details are available at: > https://builder.sourceware.org/buildbot/#builders/43/builds/196 > > Build state: failed test (failure) > Revision: 938a52c22ee915ff2cea813edd5da66bc8184885 > Worker: fedora-s390x > Build Reason: (unknown) > Blamelist: Ryan Goldberg <rgold...@redhat.com>
This isn't your fault, or that of the commit. Valgrind on the s390x testing machine got upgraded (and so did gcc). The testsuite is run under valgrind, and for some of the tests we get: vex: priv/guest_s390_toIR.c:16378 (s390_irgen_VGM): Assertion `from <= to' failed. vex storage: T total 198202912 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). This seems to be the following valgrind bug: https://bugs.kde.org/show_bug.cgi?id=470132 Luckily Andreas already suggested a patch for that. I'll try to apply that patch, install a patched valgrind on the s390x tester and rerun the elfutils buildbot. Thanks for providing a testcase for valgrind on s390x :) Cheers, Mark
