PASS: t1002-zip-aaaa.pl PASS: t1003-zip-noise.pl PASS: t1004-zip-zip64.pl PASS: t1005-zip-nonseekable.pl FAIL: t8000-valgrind-zip.pl FAIL: t8020-valgrind-ole.pl PASS: t9999-epilogue.pl ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-j4_test-20220420-221025 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-12.0.1 * clang/llvm (if any): clang version 14.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/14/bin /usr/lib/llvm/14 14.0.1 Python 3.9.12 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.60.0 [2] rust-1.60.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 11.0.14_p9 [openjdk-bin-11] 2) Eclipse Temurin JDK 8.322_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: [1] php7.4 [2] php8.0 [3] php8.1 * HEAD of ::gentoo commit ad6045fdb240ab172c06700c9060f660d9e4d540 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Apr 23 15:34:14 2022 +0000 2022-04-23 15:34:13 UTC emerge -qpvO gnome-extra/libgsf [ebuild N ] gnome-extra/libgsf-1.14.49 USE="bzip2 gtk introspection test"
Created attachment 773621 [details] emerge-info.txt
Created attachment 773624 [details] emerge-history.txt
Created attachment 773627 [details] environment
Created attachment 773630 [details] etc.portage.tar.bz2
Created attachment 773633 [details] gnome-extra:libgsf-1.14.49:20220423-162419.log
Created attachment 773636 [details] logs.tar.bz2
Created attachment 773639 [details] temp.tar.bz2
Created attachment 773642 [details] tests.tar.bz2
I can reproduce this. I strongly suspect the problem is that libraries on your system use instructions valgrind cannot handle. E.g. on my system I see: vex amd64->IR: unhandled instruction bytes: 0xC5 0xFD 0x47 0xC0 0xC5 0xE5 0x47 0xDB 0xC5 0xDD vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=1 VEX.L=1 VEX.nVVVV=0x0 ESC=0F vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==1156691== valgrind: Unrecognised instruction at address 0x40199ee. ==1156691== at 0x40199EE: _dl_sysdep_start (dl-sysdep.c:124) ==1156691== by 0x401B627: _dl_start_final (rtld.c:501) ==1156691== by 0x401B627: _dl_start (rtld.c:586) ==1156691== by 0x401A757: ??? (in /lib64/ld-linux-x86-64.so.2) ==1156691== by 0x4: ??? ==1156691== by 0x1FFF000466: ??? ==1156691== by 0x1FFF000479: ??? ==1156691== by 0x1FFF000483: ??? ==1156691== by 0x1FFF00048C: ??? ==1156691== by 0x1FFF000495: ???
Yeah, valgrind can't do AVX2 and a bunch of other things in e.g. glibc (or anywhere else). We should just skip valgrind tests where possible.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b3c63137dbc1ebc195515b18ab2a22f7a10067dd commit b3c63137dbc1ebc195515b18ab2a22f7a10067dd Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2022-05-17 02:08:40 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2022-05-17 02:09:48 +0000 gnome-extra/libgsf: Skip valgrind tests Closes: https://bugs.gentoo.org/840353 Signed-off-by: Matt Turner <mattst88@gentoo.org> .../libgsf/files/1.14.49-skip-valgrind-tests.patch | 27 ++++++++++++++++++++++ gnome-extra/libgsf/libgsf-1.14.49.ebuild | 4 ++++ 2 files changed, 31 insertions(+)
