Created attachment 751172 [details] emerge --info Emerging media-libs/mesa-21.2.5 with FEATURES=test results in a failing unit test
Created attachment 751174 [details] build.log
I think we'd need another log: Full log written to /var/tmp/portage/media-libs/mesa-21.2.5/work/mesa-21.2.5-abi_x86_32.x86/meson-logs/testlog.txt * ERROR: media-libs/mesa-21.2.5::gentoo failed (test phase):
Created attachment 777623 [details] testlog.txt from mesa-22.0.3 I hit this test failure in 22.0.3 today; here's the testlog.txt from that run. (From the top of my emerge build.log, USE="X abi_x86_32 abi_x86_64 amd64 cpu_flags_x86_sse2 elibc_glibc gles1 gles2 kernel_linux llvm lm-sensors test userland_GNU video_cards_intel xvmc zstd" and FEATURES="distcc fakeroot network-sandbox preserve-libs sandbox test userpriv usersandbox".)
Just to make clear that this is still present in versions currently in the tree, I again saw this in version 22.1.3. Of the two upstream issues added as "See Also" links, https://gitlab.freedesktop.org/mesa/mesa/-/issues/4091 looks like it's the same issue. And, prompted by the discussion there, I tried building version 22.1.2 with only ABI_X86="64", and it passed its tests. So it looks like this test only fails on ABI_X86=32.
And this (or some other failure of the same test in the same ABI) is still present in 22.1.7.
Still present in 23.2.1.
Test seems to pass when built with -O0.
*** Bug 927358 has been marked as a duplicate of this bug. ***
(In reply to Matt Turner from comment #7) > Test seems to pass when built with -O0. Test seems to pass when built with -O1 -fno-omit-frame-pointer.
I still get the same test failure in version 24.0.4 with CFLAGS="-O1 -fno-omit-frame-pointer". What USE flags are set when you see tests passing? (In particular, I wonder if you're building for the 32-bit ABI, since there's at least one package where I only encounter test failures when building for the 32-bit ABI as well as the 64-bit.)
