Created attachment 751168 [details] emerge --info Emerging sys-devel/gdb-11.1 with FEATURES=test results in many failing tests.
Created attachment 751170 [details] build.log
Thanks for filing these by the way. We need more people to run tests on packages! gdb's test suite output is rather hard to parse and I don't think it's _ever_ passed. That said, it seems to work fine at runtime. We should probably at least figure out: 1. if any of it is sandbox related 2. if they pass outside of Portage 3. if we can maybe just set a baseline of known-failing tests from what fails/passes on amd64? Any thoughts welcome *but* you do not need to be an expert/able to help with all of those things just to report bugs, I'm just thinking aloud here :) If you were willing to try outside of Portage though, that'd be welcome, just because gdb in particular has.. AFAIK, never passed, and I'd love to get to the bottom of it.
I can give it a try outside of Portage. I'm not particularly knowledgeable about gdb or its codebase (I just use it occasionally when I can't debug while running from source), but I'm happy to try things if that helps.
Created attachment 751180 [details] test output (run outside of portage) from make --jobs=32 --load-average=30 check I ran the following commands prior to running make check: $ ebuild /var/db/repos/gentoo/sys-devel/gdb/gdb-11.1.ebuild prepare # Same configure command as the ebuild runs $ ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --docdir=/usr/share/doc/gdb-11.1 --htmldir=/usr/share/doc/gdb-11.1/html --libdir=/usr/lib64 --disable-dependency-tracking --with-pkgversion=Gentoo 11.1 vanilla --with-bugurl=https://bugs.gentoo.org/ --disable-werror --disable-binutils --disable-etc --disable-gas --disable-gold --disable-gprof --disable-ld --without-debuginfod --disable-cet --enable-64-bit-bfd --disable-install-libbfd --disable-install-libiberty --enable-obsolete --disable-readline --with-system-readline --without-zlib --with-system-zlib --with-separate-debug-dir=/usr/lib/debug --with-expat --with-lzma --enable-nls --disable-source-highlight --with-python=python3.9 --without-xxhash --without-guile $ make --jobs=32 --load-average=30
Created attachment 751184 [details] test output (run outside of portage) from make check (non-parallel) I ran these commands before running make check: $ ebuild /var/db/repos/gentoo/sys-devel/gdb/gdb-11.1.ebuild clean prepare # Did not match the ebuild this time $ ./configure $ make --jobs=32 --load-average=30
That's exactly what I was going to ask you to do next (try vanilla configure + ours, and compare), so thank you! God, that looks a bit grim: ># of unexpected failures 1171 And: ># of unexpected failures 1370 Interesting that it gets fairly worse with our configure options (if I didn't mix up the order). I wonder how other distributions are running these. We might be able to run just a small subset of sane tests which are likely to work?
