* tests failing on x86_64-linux
@ 2020-12-09 18:17 Martin Sebor
2020-12-09 18:28 ` H.J. Lu
2020-12-09 19:03 ` Florian Weimer
0 siblings, 2 replies; 23+ messages in thread
From: Martin Sebor @ 2020-12-09 18:17 UTC (permalink / raw)
To: GNU C Library
I've been seeing quite a few test failures in recent builds, more
than I used to in the past. Are those expected? I configure with
no options other than --prefix=/usr and after building without
installing (i.e., just make -j16) run make -j16 check.
The results below are for the top of GCC/Glibc trunk on x86_64
Fedora Linux but I don't think using GCC 10 improves things much
if at all.
The Buildbot (http://glibc-buildbot.reserved-bit.com/waterfall)
doesn't show any useful build results except for aarch64-linux
but of those, the most recent one looks a lot cleaner than what
I see below.
http://glibc-buildbot.reserved-bit.com/builders/glibc-aarch64-linux/builds/2774/steps/check/logs/stdio
Thanks
Martin
UNSUPPORTED: assert/tst-assert-c++
UNSUPPORTED: assert/tst-assert-g++
UNSUPPORTED: debug/tst-chk4
UNSUPPORTED: debug/tst-chk5
UNSUPPORTED: debug/tst-chk6
UNSUPPORTED: debug/tst-lfschk4
UNSUPPORTED: debug/tst-lfschk5
UNSUPPORTED: debug/tst-lfschk6
UNSUPPORTED: dlfcn/bug-atexit3
UNSUPPORTED: elf/tst-audit10
UNSUPPORTED: elf/tst-avx512
FAIL: elf/tst-dlopen-self-container
FAIL: elf/tst-dlopen-tlsmodid-container
UNSUPPORTED: elf/tst-env-setuid
UNSUPPORTED: elf/tst-env-setuid-tunables
FAIL: elf/tst-glibc-hwcaps-cache
FAIL: elf/tst-glibc-hwcaps-prepend-cache
FAIL: elf/tst-ldconfig-bad-aux-cache
FAIL: elf/tst-ldconfig-ld_so_conf-update
FAIL: elf/tst-pldd
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
FAIL: locale/tst-localedef-path-norm
FAIL: localedata/tst-localedef-hardlinks
UNSUPPORTED: math/test-double-libmvec-sincos-avx512
UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
UNSUPPORTED: misc/tst-pkey
UNSUPPORTED: nptl/tst-cancel24
UNSUPPORTED: nptl/tst-cancel24-static
UNSUPPORTED: nptl/tst-minstack-throw
UNSUPPORTED: nptl/tst-once5
FAIL: nptl/tst-pthread-getattr
UNSUPPORTED: nptl/tst-thread-exit-clobber
UNSUPPORTED: nptl/tst-thread_local1
FAIL: nss/tst-nss-db-endgrent
FAIL: nss/tst-nss-db-endpwent
FAIL: nss/tst-nss-files-hosts-long
FAIL: nss/tst-nss-test3
FAIL: nss/tst-reload1
FAIL: posix/bug-ga2
UNSUPPORTED: posix/bug-ga2-mem
UNSUPPORTED: resolv/mtrace-tst-leaks2
FAIL: resolv/tst-leaks2
UNSUPPORTED: stdlib/tst-quick_exit
FAIL: stdlib/tst-system
UNSUPPORTED: stdlib/tst-thread-quick_exit
FAIL: string/tst-strerror
FAIL: string/tst-strsignal
Summary of test results:
20 FAIL
4192 PASS
26 UNSUPPORTED
16 XFAIL
2 XPASS
make[1]: *** [Makefile:642: tests] Error 1
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: tests failing on x86_64-linux 2020-12-09 18:17 tests failing on x86_64-linux Martin Sebor @ 2020-12-09 18:28 ` H.J. Lu 2020-12-09 21:17 ` Martin Sebor 2020-12-09 19:03 ` Florian Weimer 1 sibling, 1 reply; 23+ messages in thread From: H.J. Lu @ 2020-12-09 18:28 UTC (permalink / raw) To: Martin Sebor; +Cc: GNU C Library On Wed, Dec 9, 2020 at 10:17 AM Martin Sebor via Libc-alpha <libc-alpha@sourceware.org> wrote: > > I've been seeing quite a few test failures in recent builds, more > than I used to in the past. Are those expected? I configure with > no options other than --prefix=/usr and after building without > installing (i.e., just make -j16) run make -j16 check. > > The results below are for the top of GCC/Glibc trunk on x86_64 > Fedora Linux but I don't think using GCC 10 improves things much > if at all. > "make check" is clean for me on Fedora 33/x86-64. Please make sure that you have all required packages installed, including libstdc++-static. -- H.J. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux 2020-12-09 18:28 ` H.J. Lu @ 2020-12-09 21:17 ` Martin Sebor 2020-12-09 21:44 ` H.J. Lu 2020-12-16 10:21 ` tests failing on x86_64-linux Florian Weimer 0 siblings, 2 replies; 23+ messages in thread From: Martin Sebor @ 2020-12-09 21:17 UTC (permalink / raw) To: H.J. Lu, Florian Weimer; +Cc: GNU C Library On 12/9/20 11:28 AM, H.J. Lu wrote: > On Wed, Dec 9, 2020 at 10:17 AM Martin Sebor via Libc-alpha > <libc-alpha@sourceware.org> wrote: >> >> I've been seeing quite a few test failures in recent builds, more >> than I used to in the past. Are those expected? I configure with >> no options other than --prefix=/usr and after building without >> installing (i.e., just make -j16) run make -j16 check. >> >> The results below are for the top of GCC/Glibc trunk on x86_64 >> Fedora Linux but I don't think using GCC 10 improves things much >> if at all. >> > > "make check" is clean for me on Fedora 33/x86-64. Please make sure that > you have all required packages installed, including libstdc++-static. > It's been a while since I built Glibc with the system compiler so I must have misremembered the results. Here they are for my Fedora 29 machine (with libstdc++-static installed and with --prefix=/usr): gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC) UNSUPPORTED: assert/tst-assert-c++ UNSUPPORTED: assert/tst-assert-g++ UNSUPPORTED: debug/tst-chk4 UNSUPPORTED: debug/tst-chk5 UNSUPPORTED: debug/tst-chk6 UNSUPPORTED: debug/tst-lfschk4 UNSUPPORTED: debug/tst-lfschk5 UNSUPPORTED: debug/tst-lfschk6 UNSUPPORTED: dlfcn/bug-atexit3 UNSUPPORTED: elf/tst-audit10 UNSUPPORTED: elf/tst-avx512 UNSUPPORTED: elf/tst-env-setuid UNSUPPORTED: elf/tst-env-setuid-tunables XPASS: elf/tst-protected1a XPASS: elf/tst-protected1b UNSUPPORTED: math/test-double-libmvec-sincos-avx512 UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 UNSUPPORTED: misc/tst-pkey UNSUPPORTED: nptl/tst-cancel24 UNSUPPORTED: nptl/tst-cancel24-static UNSUPPORTED: nptl/tst-minstack-throw UNSUPPORTED: nptl/tst-once5 UNSUPPORTED: nptl/tst-thread-exit-clobber UNSUPPORTED: nptl/tst-thread_local1 UNSUPPORTED: stdlib/tst-quick_exit UNSUPPORTED: stdlib/tst-thread-quick_exit Summary of test results: 4214 PASS 24 UNSUPPORTED 16 XFAIL 2 XPASS And below are the results I see with today's top of GCC trunk. All the failures are due to "original exit status 127" which IIUC means the program wasn't found. Yet they're all there. Could it have something to do with the paralellization? The other difference between the native build and my GCC 11 build is that the latter is an unoptimized GCC so it takes quite a bit longer to compile. gcc version 11.0.0 20201209 (experimental) (GCC) UNSUPPORTED: assert/tst-assert-c++ UNSUPPORTED: assert/tst-assert-g++ UNSUPPORTED: debug/tst-chk4 UNSUPPORTED: debug/tst-chk5 UNSUPPORTED: debug/tst-chk6 UNSUPPORTED: debug/tst-lfschk4 UNSUPPORTED: debug/tst-lfschk5 UNSUPPORTED: debug/tst-lfschk6 UNSUPPORTED: dlfcn/bug-atexit3 UNSUPPORTED: elf/tst-audit10 UNSUPPORTED: elf/tst-avx512 FAIL: elf/tst-dlopen-self-container FAIL: elf/tst-dlopen-tlsmodid-container UNSUPPORTED: elf/tst-env-setuid UNSUPPORTED: elf/tst-env-setuid-tunables FAIL: elf/tst-glibc-hwcaps-cache FAIL: elf/tst-glibc-hwcaps-prepend-cache FAIL: elf/tst-ldconfig-bad-aux-cache FAIL: elf/tst-ldconfig-ld_so_conf-update FAIL: elf/tst-pldd XPASS: elf/tst-protected1a XPASS: elf/tst-protected1b FAIL: locale/tst-localedef-path-norm FAIL: localedata/tst-localedef-hardlinks UNSUPPORTED: math/test-double-libmvec-sincos-avx512 UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 UNSUPPORTED: misc/tst-pkey UNSUPPORTED: nptl/tst-cancel24 UNSUPPORTED: nptl/tst-cancel24-static UNSUPPORTED: nptl/tst-minstack-throw UNSUPPORTED: nptl/tst-once5 FAIL: nptl/tst-pthread-getattr UNSUPPORTED: nptl/tst-thread-exit-clobber UNSUPPORTED: nptl/tst-thread_local1 FAIL: nss/tst-nss-db-endgrent FAIL: nss/tst-nss-db-endpwent FAIL: nss/tst-nss-files-hosts-long FAIL: nss/tst-nss-test3 FAIL: nss/tst-reload1 FAIL: posix/bug-ga2 UNSUPPORTED: posix/bug-ga2-mem UNSUPPORTED: resolv/mtrace-tst-leaks2 FAIL: resolv/tst-leaks2 UNSUPPORTED: stdlib/tst-quick_exit FAIL: stdlib/tst-system UNSUPPORTED: stdlib/tst-thread-quick_exit FAIL: string/tst-strerror FAIL: string/tst-strsignal Summary of test results: 20 FAIL 4192 PASS 26 UNSUPPORTED 16 XFAIL 2 XPASS Martin ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux 2020-12-09 21:17 ` Martin Sebor @ 2020-12-09 21:44 ` H.J. Lu 2020-12-09 22:31 ` H.J. Lu 2020-12-16 10:21 ` tests failing on x86_64-linux Florian Weimer 1 sibling, 1 reply; 23+ messages in thread From: H.J. Lu @ 2020-12-09 21:44 UTC (permalink / raw) To: Martin Sebor; +Cc: Florian Weimer, GNU C Library On Wed, Dec 9, 2020 at 1:17 PM Martin Sebor <msebor@gmail.com> wrote: > > On 12/9/20 11:28 AM, H.J. Lu wrote: > > On Wed, Dec 9, 2020 at 10:17 AM Martin Sebor via Libc-alpha > > <libc-alpha@sourceware.org> wrote: > >> > >> I've been seeing quite a few test failures in recent builds, more > >> than I used to in the past. Are those expected? I configure with > >> no options other than --prefix=/usr and after building without > >> installing (i.e., just make -j16) run make -j16 check. > >> > >> The results below are for the top of GCC/Glibc trunk on x86_64 > >> Fedora Linux but I don't think using GCC 10 improves things much > >> if at all. > >> > > > > "make check" is clean for me on Fedora 33/x86-64. Please make sure that > > you have all required packages installed, including libstdc++-static. > > > > It's been a while since I built Glibc with the system compiler > so I must have misremembered the results. Here they are for > my Fedora 29 machine (with libstdc++-static installed and with > --prefix=/usr): > > gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC) > > UNSUPPORTED: assert/tst-assert-c++ > UNSUPPORTED: assert/tst-assert-g++ > UNSUPPORTED: debug/tst-chk4 > UNSUPPORTED: debug/tst-chk5 > UNSUPPORTED: debug/tst-chk6 > UNSUPPORTED: debug/tst-lfschk4 > UNSUPPORTED: debug/tst-lfschk5 > UNSUPPORTED: debug/tst-lfschk6 > UNSUPPORTED: dlfcn/bug-atexit3 > UNSUPPORTED: elf/tst-audit10 > UNSUPPORTED: elf/tst-avx512 > UNSUPPORTED: elf/tst-env-setuid > UNSUPPORTED: elf/tst-env-setuid-tunables > XPASS: elf/tst-protected1a > XPASS: elf/tst-protected1b > UNSUPPORTED: math/test-double-libmvec-sincos-avx512 > UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 > UNSUPPORTED: misc/tst-pkey > UNSUPPORTED: nptl/tst-cancel24 > UNSUPPORTED: nptl/tst-cancel24-static > UNSUPPORTED: nptl/tst-minstack-throw > UNSUPPORTED: nptl/tst-once5 > UNSUPPORTED: nptl/tst-thread-exit-clobber > UNSUPPORTED: nptl/tst-thread_local1 > UNSUPPORTED: stdlib/tst-quick_exit > UNSUPPORTED: stdlib/tst-thread-quick_exit > Summary of test results: > 4214 PASS > 24 UNSUPPORTED > 16 XFAIL > 2 XPASS > > And below are the results I see with today's top of GCC trunk. > All the failures are due to "original exit status 127" which IIUC > means the program wasn't found. Yet they're all there. Could it > have something to do with the paralellization? The other > difference between the native build and my GCC 11 build is that > the latter is an unoptimized GCC so it takes quite a bit longer > to compile. > > gcc version 11.0.0 20201209 (experimental) (GCC) Did you apply https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561332.html > UNSUPPORTED: assert/tst-assert-c++ > UNSUPPORTED: assert/tst-assert-g++ > UNSUPPORTED: debug/tst-chk4 > UNSUPPORTED: debug/tst-chk5 > UNSUPPORTED: debug/tst-chk6 > UNSUPPORTED: debug/tst-lfschk4 > UNSUPPORTED: debug/tst-lfschk5 > UNSUPPORTED: debug/tst-lfschk6 > UNSUPPORTED: dlfcn/bug-atexit3 > UNSUPPORTED: elf/tst-audit10 > UNSUPPORTED: elf/tst-avx512 > FAIL: elf/tst-dlopen-self-container > FAIL: elf/tst-dlopen-tlsmodid-container > UNSUPPORTED: elf/tst-env-setuid > UNSUPPORTED: elf/tst-env-setuid-tunables > FAIL: elf/tst-glibc-hwcaps-cache > FAIL: elf/tst-glibc-hwcaps-prepend-cache > FAIL: elf/tst-ldconfig-bad-aux-cache > FAIL: elf/tst-ldconfig-ld_so_conf-update > FAIL: elf/tst-pldd > XPASS: elf/tst-protected1a > XPASS: elf/tst-protected1b > FAIL: locale/tst-localedef-path-norm > FAIL: localedata/tst-localedef-hardlinks > UNSUPPORTED: math/test-double-libmvec-sincos-avx512 > UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 > UNSUPPORTED: misc/tst-pkey > UNSUPPORTED: nptl/tst-cancel24 > UNSUPPORTED: nptl/tst-cancel24-static > UNSUPPORTED: nptl/tst-minstack-throw > UNSUPPORTED: nptl/tst-once5 > FAIL: nptl/tst-pthread-getattr > UNSUPPORTED: nptl/tst-thread-exit-clobber > UNSUPPORTED: nptl/tst-thread_local1 > FAIL: nss/tst-nss-db-endgrent > FAIL: nss/tst-nss-db-endpwent > FAIL: nss/tst-nss-files-hosts-long > FAIL: nss/tst-nss-test3 > FAIL: nss/tst-reload1 > FAIL: posix/bug-ga2 > UNSUPPORTED: posix/bug-ga2-mem > UNSUPPORTED: resolv/mtrace-tst-leaks2 > FAIL: resolv/tst-leaks2 > UNSUPPORTED: stdlib/tst-quick_exit > FAIL: stdlib/tst-system > UNSUPPORTED: stdlib/tst-thread-quick_exit > FAIL: string/tst-strerror > FAIL: string/tst-strsignal > Summary of test results: > 20 FAIL > 4192 PASS > 26 UNSUPPORTED > 16 XFAIL > 2 XPASS > > Martin -- H.J. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux 2020-12-09 21:44 ` H.J. Lu @ 2020-12-09 22:31 ` H.J. Lu 2020-12-10 2:50 ` H.J. Lu 0 siblings, 1 reply; 23+ messages in thread From: H.J. Lu @ 2020-12-09 22:31 UTC (permalink / raw) To: Martin Sebor; +Cc: Florian Weimer, GNU C Library On Wed, Dec 9, 2020 at 1:44 PM H.J. Lu <hjl.tools@gmail.com> wrote: > > On Wed, Dec 9, 2020 at 1:17 PM Martin Sebor <msebor@gmail.com> wrote: > > > > On 12/9/20 11:28 AM, H.J. Lu wrote: > > > On Wed, Dec 9, 2020 at 10:17 AM Martin Sebor via Libc-alpha > > > <libc-alpha@sourceware.org> wrote: > > >> > > >> I've been seeing quite a few test failures in recent builds, more > > >> than I used to in the past. Are those expected? I configure with > > >> no options other than --prefix=/usr and after building without > > >> installing (i.e., just make -j16) run make -j16 check. > > >> > > >> The results below are for the top of GCC/Glibc trunk on x86_64 > > >> Fedora Linux but I don't think using GCC 10 improves things much > > >> if at all. > > >> > > > > > > "make check" is clean for me on Fedora 33/x86-64. Please make sure that > > > you have all required packages installed, including libstdc++-static. > > > > > > > It's been a while since I built Glibc with the system compiler > > so I must have misremembered the results. Here they are for > > my Fedora 29 machine (with libstdc++-static installed and with > > --prefix=/usr): > > > > gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC) > > > > UNSUPPORTED: assert/tst-assert-c++ > > UNSUPPORTED: assert/tst-assert-g++ > > UNSUPPORTED: debug/tst-chk4 > > UNSUPPORTED: debug/tst-chk5 > > UNSUPPORTED: debug/tst-chk6 > > UNSUPPORTED: debug/tst-lfschk4 > > UNSUPPORTED: debug/tst-lfschk5 > > UNSUPPORTED: debug/tst-lfschk6 > > UNSUPPORTED: dlfcn/bug-atexit3 > > UNSUPPORTED: elf/tst-audit10 > > UNSUPPORTED: elf/tst-avx512 > > UNSUPPORTED: elf/tst-env-setuid > > UNSUPPORTED: elf/tst-env-setuid-tunables > > XPASS: elf/tst-protected1a > > XPASS: elf/tst-protected1b > > UNSUPPORTED: math/test-double-libmvec-sincos-avx512 > > UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 > > UNSUPPORTED: misc/tst-pkey > > UNSUPPORTED: nptl/tst-cancel24 > > UNSUPPORTED: nptl/tst-cancel24-static > > UNSUPPORTED: nptl/tst-minstack-throw > > UNSUPPORTED: nptl/tst-once5 > > UNSUPPORTED: nptl/tst-thread-exit-clobber > > UNSUPPORTED: nptl/tst-thread_local1 > > UNSUPPORTED: stdlib/tst-quick_exit > > UNSUPPORTED: stdlib/tst-thread-quick_exit > > Summary of test results: > > 4214 PASS > > 24 UNSUPPORTED > > 16 XFAIL > > 2 XPASS > > > > And below are the results I see with today's top of GCC trunk. > > All the failures are due to "original exit status 127" which IIUC > > means the program wasn't found. Yet they're all there. Could it > > have something to do with the paralellization? The other > > difference between the native build and my GCC 11 build is that > > the latter is an unoptimized GCC so it takes quite a bit longer > > to compile. > > > > gcc version 11.0.0 20201209 (experimental) (GCC) > > Did you apply > > https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561332.html Using built-in specs. COLLECT_GCC=/usr/gcc-11.0.0-x32/bin/gcc COLLECT_LTO_WRAPPER=/usr/gcc-11.0.0-x32/libexec/gcc/x86_64-pc-linux-gnu/11.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /export/gnu/import/git/gitlab/x86-gcc/configure --enable-cet --with-demangler-in-ld --prefix=/usr/gcc-11.0.0-x32 --with-local-prefix=/usr/local --enable-gnu-indirect-function --enable-clocale=gnu --with-system-zlib --with-target-system-zlib --with-fpmath=sse --with-multilib-list=m32,m64,mx32 --enable-linker-build-id --enable-gnu-unique-object --enable-languages=c,c++,fortran,lto,objc,obj-c++,go Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.0.0 20201204 (experimental) (GCC) is "makc check" clean. I will test r11-5888 + my PR target/98146 patches. -- H.J. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux 2020-12-09 22:31 ` H.J. Lu @ 2020-12-10 2:50 ` H.J. Lu 2020-12-15 0:55 ` Martin Sebor 0 siblings, 1 reply; 23+ messages in thread From: H.J. Lu @ 2020-12-10 2:50 UTC (permalink / raw) To: Martin Sebor; +Cc: Florian Weimer, GNU C Library On Wed, Dec 9, 2020 at 2:31 PM H.J. Lu <hjl.tools@gmail.com> wrote: > > On Wed, Dec 9, 2020 at 1:44 PM H.J. Lu <hjl.tools@gmail.com> wrote: > > > > On Wed, Dec 9, 2020 at 1:17 PM Martin Sebor <msebor@gmail.com> wrote: > > > > > > On 12/9/20 11:28 AM, H.J. Lu wrote: > > > > On Wed, Dec 9, 2020 at 10:17 AM Martin Sebor via Libc-alpha > > > > <libc-alpha@sourceware.org> wrote: > > > >> > > > >> I've been seeing quite a few test failures in recent builds, more > > > >> than I used to in the past. Are those expected? I configure with > > > >> no options other than --prefix=/usr and after building without > > > >> installing (i.e., just make -j16) run make -j16 check. > > > >> > > > >> The results below are for the top of GCC/Glibc trunk on x86_64 > > > >> Fedora Linux but I don't think using GCC 10 improves things much > > > >> if at all. > > > >> > > > > > > > > "make check" is clean for me on Fedora 33/x86-64. Please make sure that > > > > you have all required packages installed, including libstdc++-static. > > > > > > > > > > It's been a while since I built Glibc with the system compiler > > > so I must have misremembered the results. Here they are for > > > my Fedora 29 machine (with libstdc++-static installed and with > > > --prefix=/usr): > > > > > > gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC) > > > > > > UNSUPPORTED: assert/tst-assert-c++ > > > UNSUPPORTED: assert/tst-assert-g++ > > > UNSUPPORTED: debug/tst-chk4 > > > UNSUPPORTED: debug/tst-chk5 > > > UNSUPPORTED: debug/tst-chk6 > > > UNSUPPORTED: debug/tst-lfschk4 > > > UNSUPPORTED: debug/tst-lfschk5 > > > UNSUPPORTED: debug/tst-lfschk6 > > > UNSUPPORTED: dlfcn/bug-atexit3 > > > UNSUPPORTED: elf/tst-audit10 > > > UNSUPPORTED: elf/tst-avx512 > > > UNSUPPORTED: elf/tst-env-setuid > > > UNSUPPORTED: elf/tst-env-setuid-tunables > > > XPASS: elf/tst-protected1a > > > XPASS: elf/tst-protected1b > > > UNSUPPORTED: math/test-double-libmvec-sincos-avx512 > > > UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 > > > UNSUPPORTED: misc/tst-pkey > > > UNSUPPORTED: nptl/tst-cancel24 > > > UNSUPPORTED: nptl/tst-cancel24-static > > > UNSUPPORTED: nptl/tst-minstack-throw > > > UNSUPPORTED: nptl/tst-once5 > > > UNSUPPORTED: nptl/tst-thread-exit-clobber > > > UNSUPPORTED: nptl/tst-thread_local1 > > > UNSUPPORTED: stdlib/tst-quick_exit > > > UNSUPPORTED: stdlib/tst-thread-quick_exit > > > Summary of test results: > > > 4214 PASS > > > 24 UNSUPPORTED > > > 16 XFAIL > > > 2 XPASS > > > > > > And below are the results I see with today's top of GCC trunk. > > > All the failures are due to "original exit status 127" which IIUC > > > means the program wasn't found. Yet they're all there. Could it > > > have something to do with the paralellization? The other > > > difference between the native build and my GCC 11 build is that > > > the latter is an unoptimized GCC so it takes quite a bit longer > > > to compile. > > > > > > gcc version 11.0.0 20201209 (experimental) (GCC) > > > > Did you apply > > > > https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561332.html > > Using built-in specs. > COLLECT_GCC=/usr/gcc-11.0.0-x32/bin/gcc > COLLECT_LTO_WRAPPER=/usr/gcc-11.0.0-x32/libexec/gcc/x86_64-pc-linux-gnu/11.0.0/lto-wrapper > Target: x86_64-pc-linux-gnu > Configured with: /export/gnu/import/git/gitlab/x86-gcc/configure > --enable-cet --with-demangler-in-ld --prefix=/usr/gcc-11.0.0-x32 > --with-local-prefix=/usr/local --enable-gnu-indirect-function > --enable-clocale=gnu --with-system-zlib --with-target-system-zlib > --with-fpmath=sse --with-multilib-list=m32,m64,mx32 > --enable-linker-build-id --enable-gnu-unique-object > --enable-languages=c,c++,fortran,lto,objc,obj-c++,go > Thread model: posix > Supported LTO compression algorithms: zlib zstd > gcc version 11.0.0 20201204 (experimental) (GCC) > > is "makc check" clean. I will test r11-5888 + my PR target/98146 patches. r11-5888 is also "make check" clean. -- H.J. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux 2020-12-10 2:50 ` H.J. Lu @ 2020-12-15 0:55 ` Martin Sebor 2021-04-28 20:07 ` tests failing on x86_64-linux (due to test-container?) Martin Sebor 0 siblings, 1 reply; 23+ messages in thread From: Martin Sebor @ 2020-12-15 0:55 UTC (permalink / raw) To: H.J. Lu; +Cc: Florian Weimer, GNU C Library On 12/9/20 7:50 PM, H.J. Lu wrote: > On Wed, Dec 9, 2020 at 2:31 PM H.J. Lu <hjl.tools@gmail.com> wrote: >> >> On Wed, Dec 9, 2020 at 1:44 PM H.J. Lu <hjl.tools@gmail.com> wrote: >>> >>> On Wed, Dec 9, 2020 at 1:17 PM Martin Sebor <msebor@gmail.com> wrote: >>>> >>>> On 12/9/20 11:28 AM, H.J. Lu wrote: >>>>> On Wed, Dec 9, 2020 at 10:17 AM Martin Sebor via Libc-alpha >>>>> <libc-alpha@sourceware.org> wrote: >>>>>> >>>>>> I've been seeing quite a few test failures in recent builds, more >>>>>> than I used to in the past. Are those expected? I configure with >>>>>> no options other than --prefix=/usr and after building without >>>>>> installing (i.e., just make -j16) run make -j16 check. >>>>>> >>>>>> The results below are for the top of GCC/Glibc trunk on x86_64 >>>>>> Fedora Linux but I don't think using GCC 10 improves things much >>>>>> if at all. >>>>>> >>>>> >>>>> "make check" is clean for me on Fedora 33/x86-64. Please make sure that >>>>> you have all required packages installed, including libstdc++-static. >>>>> >>>> >>>> It's been a while since I built Glibc with the system compiler >>>> so I must have misremembered the results. Here they are for >>>> my Fedora 29 machine (with libstdc++-static installed and with >>>> --prefix=/usr): >>>> >>>> gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC) >>>> >>>> UNSUPPORTED: assert/tst-assert-c++ >>>> UNSUPPORTED: assert/tst-assert-g++ >>>> UNSUPPORTED: debug/tst-chk4 >>>> UNSUPPORTED: debug/tst-chk5 >>>> UNSUPPORTED: debug/tst-chk6 >>>> UNSUPPORTED: debug/tst-lfschk4 >>>> UNSUPPORTED: debug/tst-lfschk5 >>>> UNSUPPORTED: debug/tst-lfschk6 >>>> UNSUPPORTED: dlfcn/bug-atexit3 >>>> UNSUPPORTED: elf/tst-audit10 >>>> UNSUPPORTED: elf/tst-avx512 >>>> UNSUPPORTED: elf/tst-env-setuid >>>> UNSUPPORTED: elf/tst-env-setuid-tunables >>>> XPASS: elf/tst-protected1a >>>> XPASS: elf/tst-protected1b >>>> UNSUPPORTED: math/test-double-libmvec-sincos-avx512 >>>> UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 >>>> UNSUPPORTED: misc/tst-pkey >>>> UNSUPPORTED: nptl/tst-cancel24 >>>> UNSUPPORTED: nptl/tst-cancel24-static >>>> UNSUPPORTED: nptl/tst-minstack-throw >>>> UNSUPPORTED: nptl/tst-once5 >>>> UNSUPPORTED: nptl/tst-thread-exit-clobber >>>> UNSUPPORTED: nptl/tst-thread_local1 >>>> UNSUPPORTED: stdlib/tst-quick_exit >>>> UNSUPPORTED: stdlib/tst-thread-quick_exit >>>> Summary of test results: >>>> 4214 PASS >>>> 24 UNSUPPORTED >>>> 16 XFAIL >>>> 2 XPASS >>>> >>>> And below are the results I see with today's top of GCC trunk. >>>> All the failures are due to "original exit status 127" which IIUC >>>> means the program wasn't found. Yet they're all there. Could it >>>> have something to do with the paralellization? The other >>>> difference between the native build and my GCC 11 build is that >>>> the latter is an unoptimized GCC so it takes quite a bit longer >>>> to compile. >>>> >>>> gcc version 11.0.0 20201209 (experimental) (GCC) >>> >>> Did you apply >>> >>> https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561332.html >> >> Using built-in specs. >> COLLECT_GCC=/usr/gcc-11.0.0-x32/bin/gcc >> COLLECT_LTO_WRAPPER=/usr/gcc-11.0.0-x32/libexec/gcc/x86_64-pc-linux-gnu/11.0.0/lto-wrapper >> Target: x86_64-pc-linux-gnu >> Configured with: /export/gnu/import/git/gitlab/x86-gcc/configure >> --enable-cet --with-demangler-in-ld --prefix=/usr/gcc-11.0.0-x32 >> --with-local-prefix=/usr/local --enable-gnu-indirect-function >> --enable-clocale=gnu --with-system-zlib --with-target-system-zlib >> --with-fpmath=sse --with-multilib-list=m32,m64,mx32 >> --enable-linker-build-id --enable-gnu-unique-object >> --enable-languages=c,c++,fortran,lto,objc,obj-c++,go >> Thread model: posix >> Supported LTO compression algorithms: zlib zstd >> gcc version 11.0.0 20201204 (experimental) (GCC) >> >> is "makc check" clean. I will test r11-5888 + my PR target/98146 patches. > > r11-5888 is also "make check" clean. I still see the same failures with today's top of trunk and two more: UNSUPPORTED: assert/tst-assert-c++ UNSUPPORTED: assert/tst-assert-g++ UNSUPPORTED: debug/tst-chk4 UNSUPPORTED: debug/tst-chk5 UNSUPPORTED: debug/tst-chk6 UNSUPPORTED: debug/tst-lfschk4 UNSUPPORTED: debug/tst-lfschk5 UNSUPPORTED: debug/tst-lfschk6 UNSUPPORTED: dlfcn/bug-atexit3 UNSUPPORTED: elf/tst-audit10 UNSUPPORTED: elf/tst-avx512 FAIL: elf/tst-dlopen-self-container FAIL: elf/tst-dlopen-tlsmodid-container UNSUPPORTED: elf/tst-env-setuid UNSUPPORTED: elf/tst-env-setuid-tunables FAIL: elf/tst-glibc-hwcaps-cache FAIL: elf/tst-glibc-hwcaps-prepend-cache FAIL: elf/tst-ldconfig-bad-aux-cache FAIL: elf/tst-ldconfig-ld_so_conf-update FAIL: elf/tst-pldd FAIL: elf/tst-preload-pthread-libc XPASS: elf/tst-protected1a XPASS: elf/tst-protected1b FAIL: grp/tst-initgroups1 <<< new FAIL: grp/tst-initgroups2 <<< new FAIL: locale/tst-localedef-path-norm FAIL: localedata/tst-localedef-hardlinks UNSUPPORTED: math/test-double-libmvec-sincos-avx512 UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 UNSUPPORTED: misc/tst-pkey UNSUPPORTED: nptl/tst-cancel24 UNSUPPORTED: nptl/tst-cancel24-static UNSUPPORTED: nptl/tst-minstack-throw UNSUPPORTED: nptl/tst-once5 FAIL: nptl/tst-pthread-getattr UNSUPPORTED: nptl/tst-thread-exit-clobber UNSUPPORTED: nptl/tst-thread_local1 FAIL: nss/tst-nss-db-endgrent FAIL: nss/tst-nss-db-endpwent FAIL: nss/tst-nss-files-hosts-long FAIL: nss/tst-nss-test3 FAIL: nss/tst-reload1 FAIL: posix/bug-ga2 UNSUPPORTED: posix/bug-ga2-mem UNSUPPORTED: resolv/mtrace-tst-leaks2 FAIL: resolv/tst-leaks2 UNSUPPORTED: stdlib/tst-quick_exit FAIL: stdlib/tst-system UNSUPPORTED: stdlib/tst-thread-quick_exit FAIL: string/tst-strerror FAIL: string/tst-strsignal Summary of test results: 23 FAIL 4192 PASS 26 UNSUPPORTED 16 XFAIL 2 XPASS Martin ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2020-12-15 0:55 ` Martin Sebor @ 2021-04-28 20:07 ` Martin Sebor 2021-04-28 20:37 ` DJ Delorie 0 siblings, 1 reply; 23+ messages in thread From: Martin Sebor @ 2021-04-28 20:07 UTC (permalink / raw) To: GNU C Library I still keep seeing many failures in Glibc tests. The set from last night with GCC 11 is below. I tried to figure out if the failing tests had something in common. It seems that they are all invoked via test-container. I'm still using stock Fedora release 29. Is there something I might need to install to get it to work properly? Otherwise any suggestions on how to (quickly) debug it? I don't see any errors or messages in the log suggesting what the problem might be. UNSUPPORTED: assert/tst-assert-c++ UNSUPPORTED: assert/tst-assert-g++ UNSUPPORTED: debug/tst-chk4 UNSUPPORTED: debug/tst-chk5 UNSUPPORTED: debug/tst-chk6 UNSUPPORTED: debug/tst-lfschk4 UNSUPPORTED: debug/tst-lfschk5 UNSUPPORTED: debug/tst-lfschk6 UNSUPPORTED: dlfcn/bug-atexit3 UNSUPPORTED: elf/tst-audit10 UNSUPPORTED: elf/tst-avx512 FAIL: elf/tst-dlopen-self-container FAIL: elf/tst-dlopen-tlsmodid-container UNSUPPORTED: elf/tst-env-setuid UNSUPPORTED: elf/tst-env-setuid-tunables FAIL: elf/tst-glibc-hwcaps-cache FAIL: elf/tst-glibc-hwcaps-prepend-cache FAIL: elf/tst-ldconfig-bad-aux-cache FAIL: elf/tst-ldconfig-ld_so_conf-update FAIL: elf/tst-pldd FAIL: elf/tst-preload-pthread-libc XPASS: elf/tst-protected1a XPASS: elf/tst-protected1b FAIL: grp/tst-initgroups1 FAIL: grp/tst-initgroups2 FAIL: locale/tst-localedef-path-norm FAIL: localedata/tst-localedef-hardlinks UNSUPPORTED: math/test-double-libmvec-sincos-avx512 UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 UNSUPPORTED: misc/tst-adjtimex UNSUPPORTED: misc/tst-clock_adjtime UNSUPPORTED: misc/tst-ntp_adjtime UNSUPPORTED: misc/tst-pkey UNSUPPORTED: nptl/tst-cancel24 UNSUPPORTED: nptl/tst-cancel24-static UNSUPPORTED: nptl/tst-minstack-throw UNSUPPORTED: nptl/tst-once5 FAIL: nptl/tst-pthread-getattr UNSUPPORTED: nptl/tst-thread-exit-clobber UNSUPPORTED: nptl/tst-thread_local1 FAIL: nss/tst-nss-compat1 FAIL: nss/tst-nss-db-endgrent FAIL: nss/tst-nss-db-endpwent FAIL: nss/tst-nss-files-hosts-long FAIL: nss/tst-nss-test3 FAIL: nss/tst-reload1 FAIL: nss/tst-reload2 FAIL: posix/bug-ga2 UNSUPPORTED: posix/bug-ga2-mem UNSUPPORTED: resolv/mtrace-tst-leaks2 FAIL: resolv/tst-leaks2 UNSUPPORTED: stdlib/tst-quick_exit UNSUPPORTED: stdlib/tst-secure-getenv FAIL: stdlib/tst-system UNSUPPORTED: stdlib/tst-thread-quick_exit FAIL: string/tst-strerror FAIL: string/tst-strsignal UNSUPPORTED: time/tst-clock_settime UNSUPPORTED: time/tst-settimeofday Summary of test results: 25 FAIL 4287 PASS 32 UNSUPPORTED 16 XFAIL 2 XPASS make[1]: *** [Makefile:642: tests] Error 1 make[1]: Leaving directory '/ssd/src/glibc' make: *** [Makefile:9: check] Error 2 make: Leaving directory '/ssd/build/glibc' On 12/14/20 5:55 PM, Martin Sebor wrote: > On 12/9/20 7:50 PM, H.J. Lu wrote: >> On Wed, Dec 9, 2020 at 2:31 PM H.J. Lu <hjl.tools@gmail.com> wrote: >>> >>> On Wed, Dec 9, 2020 at 1:44 PM H.J. Lu <hjl.tools@gmail.com> wrote: >>>> >>>> On Wed, Dec 9, 2020 at 1:17 PM Martin Sebor <msebor@gmail.com> wrote: >>>>> >>>>> On 12/9/20 11:28 AM, H.J. Lu wrote: >>>>>> On Wed, Dec 9, 2020 at 10:17 AM Martin Sebor via Libc-alpha >>>>>> <libc-alpha@sourceware.org> wrote: >>>>>>> >>>>>>> I've been seeing quite a few test failures in recent builds, more >>>>>>> than I used to in the past. Are those expected? I configure with >>>>>>> no options other than --prefix=/usr and after building without >>>>>>> installing (i.e., just make -j16) run make -j16 check. >>>>>>> >>>>>>> The results below are for the top of GCC/Glibc trunk on x86_64 >>>>>>> Fedora Linux but I don't think using GCC 10 improves things much >>>>>>> if at all. >>>>>>> >>>>>> >>>>>> "make check" is clean for me on Fedora 33/x86-64. Please make >>>>>> sure that >>>>>> you have all required packages installed, including libstdc++-static. >>>>>> >>>>> >>>>> It's been a while since I built Glibc with the system compiler >>>>> so I must have misremembered the results. Here they are for >>>>> my Fedora 29 machine (with libstdc++-static installed and with >>>>> --prefix=/usr): >>>>> >>>>> gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC) >>>>> >>>>> UNSUPPORTED: assert/tst-assert-c++ >>>>> UNSUPPORTED: assert/tst-assert-g++ >>>>> UNSUPPORTED: debug/tst-chk4 >>>>> UNSUPPORTED: debug/tst-chk5 >>>>> UNSUPPORTED: debug/tst-chk6 >>>>> UNSUPPORTED: debug/tst-lfschk4 >>>>> UNSUPPORTED: debug/tst-lfschk5 >>>>> UNSUPPORTED: debug/tst-lfschk6 >>>>> UNSUPPORTED: dlfcn/bug-atexit3 >>>>> UNSUPPORTED: elf/tst-audit10 >>>>> UNSUPPORTED: elf/tst-avx512 >>>>> UNSUPPORTED: elf/tst-env-setuid >>>>> UNSUPPORTED: elf/tst-env-setuid-tunables >>>>> XPASS: elf/tst-protected1a >>>>> XPASS: elf/tst-protected1b >>>>> UNSUPPORTED: math/test-double-libmvec-sincos-avx512 >>>>> UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 >>>>> UNSUPPORTED: misc/tst-pkey >>>>> UNSUPPORTED: nptl/tst-cancel24 >>>>> UNSUPPORTED: nptl/tst-cancel24-static >>>>> UNSUPPORTED: nptl/tst-minstack-throw >>>>> UNSUPPORTED: nptl/tst-once5 >>>>> UNSUPPORTED: nptl/tst-thread-exit-clobber >>>>> UNSUPPORTED: nptl/tst-thread_local1 >>>>> UNSUPPORTED: stdlib/tst-quick_exit >>>>> UNSUPPORTED: stdlib/tst-thread-quick_exit >>>>> Summary of test results: >>>>> 4214 PASS >>>>> 24 UNSUPPORTED >>>>> 16 XFAIL >>>>> 2 XPASS >>>>> >>>>> And below are the results I see with today's top of GCC trunk. >>>>> All the failures are due to "original exit status 127" which IIUC >>>>> means the program wasn't found. Yet they're all there. Could it >>>>> have something to do with the paralellization? The other >>>>> difference between the native build and my GCC 11 build is that >>>>> the latter is an unoptimized GCC so it takes quite a bit longer >>>>> to compile. >>>>> >>>>> gcc version 11.0.0 20201209 (experimental) (GCC) >>>> >>>> Did you apply >>>> >>>> https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561332.html >>> >>> Using built-in specs. >>> COLLECT_GCC=/usr/gcc-11.0.0-x32/bin/gcc >>> COLLECT_LTO_WRAPPER=/usr/gcc-11.0.0-x32/libexec/gcc/x86_64-pc-linux-gnu/11.0.0/lto-wrapper >>> >>> Target: x86_64-pc-linux-gnu >>> Configured with: /export/gnu/import/git/gitlab/x86-gcc/configure >>> --enable-cet --with-demangler-in-ld --prefix=/usr/gcc-11.0.0-x32 >>> --with-local-prefix=/usr/local --enable-gnu-indirect-function >>> --enable-clocale=gnu --with-system-zlib --with-target-system-zlib >>> --with-fpmath=sse --with-multilib-list=m32,m64,mx32 >>> --enable-linker-build-id --enable-gnu-unique-object >>> --enable-languages=c,c++,fortran,lto,objc,obj-c++,go >>> Thread model: posix >>> Supported LTO compression algorithms: zlib zstd >>> gcc version 11.0.0 20201204 (experimental) (GCC) >>> >>> is "makc check" clean. I will test r11-5888 + my PR target/98146 >>> patches. >> >> r11-5888 is also "make check" clean. > > I still see the same failures with today's top of trunk and two > more: > > UNSUPPORTED: assert/tst-assert-c++ > UNSUPPORTED: assert/tst-assert-g++ > UNSUPPORTED: debug/tst-chk4 > UNSUPPORTED: debug/tst-chk5 > UNSUPPORTED: debug/tst-chk6 > UNSUPPORTED: debug/tst-lfschk4 > UNSUPPORTED: debug/tst-lfschk5 > UNSUPPORTED: debug/tst-lfschk6 > UNSUPPORTED: dlfcn/bug-atexit3 > UNSUPPORTED: elf/tst-audit10 > UNSUPPORTED: elf/tst-avx512 > FAIL: elf/tst-dlopen-self-container > FAIL: elf/tst-dlopen-tlsmodid-container > UNSUPPORTED: elf/tst-env-setuid > UNSUPPORTED: elf/tst-env-setuid-tunables > FAIL: elf/tst-glibc-hwcaps-cache > FAIL: elf/tst-glibc-hwcaps-prepend-cache > FAIL: elf/tst-ldconfig-bad-aux-cache > FAIL: elf/tst-ldconfig-ld_so_conf-update > FAIL: elf/tst-pldd > FAIL: elf/tst-preload-pthread-libc > XPASS: elf/tst-protected1a > XPASS: elf/tst-protected1b > FAIL: grp/tst-initgroups1 <<< new > FAIL: grp/tst-initgroups2 <<< new > FAIL: locale/tst-localedef-path-norm > FAIL: localedata/tst-localedef-hardlinks > UNSUPPORTED: math/test-double-libmvec-sincos-avx512 > UNSUPPORTED: math/test-float-libmvec-sincosf-avx512 > UNSUPPORTED: misc/tst-pkey > UNSUPPORTED: nptl/tst-cancel24 > UNSUPPORTED: nptl/tst-cancel24-static > UNSUPPORTED: nptl/tst-minstack-throw > UNSUPPORTED: nptl/tst-once5 > FAIL: nptl/tst-pthread-getattr > UNSUPPORTED: nptl/tst-thread-exit-clobber > UNSUPPORTED: nptl/tst-thread_local1 > FAIL: nss/tst-nss-db-endgrent > FAIL: nss/tst-nss-db-endpwent > FAIL: nss/tst-nss-files-hosts-long > FAIL: nss/tst-nss-test3 > FAIL: nss/tst-reload1 > FAIL: posix/bug-ga2 > UNSUPPORTED: posix/bug-ga2-mem > UNSUPPORTED: resolv/mtrace-tst-leaks2 > FAIL: resolv/tst-leaks2 > UNSUPPORTED: stdlib/tst-quick_exit > FAIL: stdlib/tst-system > UNSUPPORTED: stdlib/tst-thread-quick_exit > FAIL: string/tst-strerror > FAIL: string/tst-strsignal > Summary of test results: > 23 FAIL > 4192 PASS > 26 UNSUPPORTED > 16 XFAIL > 2 XPASS > > Martin ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2021-04-28 20:07 ` tests failing on x86_64-linux (due to test-container?) Martin Sebor @ 2021-04-28 20:37 ` DJ Delorie 2021-04-28 21:50 ` Martin Sebor 0 siblings, 1 reply; 23+ messages in thread From: DJ Delorie @ 2021-04-28 20:37 UTC (permalink / raw) To: Martin Sebor; +Cc: libc-alpha The test-container binary should print its own diagnostics, although they may show up in the build logs instead of the test logs (stderr vs stdout). You can "make test t=nss/tst-nss-test3" to re-run one test and see the output. (also, "make help" tells you the above) ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2021-04-28 20:37 ` DJ Delorie @ 2021-04-28 21:50 ` Martin Sebor 2021-04-28 23:08 ` DJ Delorie 0 siblings, 1 reply; 23+ messages in thread From: Martin Sebor @ 2021-04-28 21:50 UTC (permalink / raw) To: DJ Delorie; +Cc: libc-alpha On 4/28/21 2:37 PM, DJ Delorie wrote: > > The test-container binary should print its own diagnostics, although > they may show up in the build logs instead of the test logs (stderr vs > stdout). > > You can "make test t=nss/tst-nss-test3" to re-run one test and see the > output. Aha! A new trick! Thanks! I've been using nice make -C /build/glibc check subdirs=nss tests=tst-nss-test3 Either way, the error is the same (I thought I had mentioned it before but maybe not): /build/glibc/nss/tst-nss-test3: error while loading shared libraries: /build/glibc/nss/tst-nss-test3: cannot open shared object file: No such file or directory Not sure what .so it's looking for though. > > (also, "make help" tells you the above) Nice. I didn't know about this one either. Thank you again! Martin ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2021-04-28 21:50 ` Martin Sebor @ 2021-04-28 23:08 ` DJ Delorie 2021-04-28 23:42 ` Martin Sebor 0 siblings, 1 reply; 23+ messages in thread From: DJ Delorie @ 2021-04-28 23:08 UTC (permalink / raw) To: Martin Sebor; +Cc: libc-alpha Martin Sebor <msebor@gmail.com> writes: > /build/glibc/nss/tst-nss-test3: error while loading shared libraries: > /build/glibc/nss/tst-nss-test3: cannot open shared object file: No such > file or directory > > Not sure what .so it's looking for though. That would be "/build/glibc/nss/tst-nss-test3" ;-) (which should be bind-mounted inside your test chroot, which would be /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) You can strace the test, if you're root, with "strace -f -o /tmp/foo make test ..." You can also run "capsh --print" to make sure you have all the capabilities you expect. IIRC cap_sys_admin and cap_sys_chroot are key, along with cap_mknod, and maybe cap_setgid and cap_setuid. Also, selinux might be interfering. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2021-04-28 23:08 ` DJ Delorie @ 2021-04-28 23:42 ` Martin Sebor 2021-04-28 23:54 ` DJ Delorie 0 siblings, 1 reply; 23+ messages in thread From: Martin Sebor @ 2021-04-28 23:42 UTC (permalink / raw) To: DJ Delorie; +Cc: libc-alpha On 4/28/21 5:08 PM, DJ Delorie wrote: > > Martin Sebor <msebor@gmail.com> writes: >> /build/glibc/nss/tst-nss-test3: error while loading shared libraries: >> /build/glibc/nss/tst-nss-test3: cannot open shared object file: No such >> file or directory >> >> Not sure what .so it's looking for though. > > That would be "/build/glibc/nss/tst-nss-test3" ;-) Aaah. tst-nss-test3 is failing to open itself. Poor thing must be lost. ;) > > (which should be bind-mounted inside your test chroot, which would be > /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) /build/glibc/testroot.root/build/glibc/ is empty. > > You can strace the test, if you're root, with "strace -f -o /tmp/foo > make test ..." With this as root I get: error: test-container.c:235: can't mount /ssd/src/glibc onto /build/glibc/testroot.root/ssd/src/glibc The strace log before the error shows this (I don't see anything suspicious before that): 31182 getuid() = 0 31182 getgid() = 0 31182 openat(AT_FDCWD, "/ssd/build/glibc/elf/ld-linux-x86-64.so.2.root/ld-linux-x86-64.so.2.script", O_RDONLY) = -1 ENOENT (No such file or directory) 31182 openat(AT_FDCWD, "/ssd/build/glibc/elf/ld-linux-x86-64.so.2.script", O_RDONLY) = -1 ENOENT (No such file or directory) 31182 unshare(CLONE_NEWNS|CLONE_NEWUSER|CLONE_NEWPID) = 0 31182 mount("none", "/", NULL, MS_REC|MS_PRIVATE, NULL) = 0 31182 mount("/ssd/src/glibc", "/build/glibc/testroot.root/ssd/src/glibc", 0x40927f, MS_BIND, NULL) = -1 EACCES (Permission denied) 31182 write(1, "error: test-container.c:235: ", 29) = 29 31182 write(1, "can't mount /ssd/src/glibc onto "..., 73) = 73 31182 write(1, "\n", 1) = 1 31182 exit_group(1) = ? 31182 +++ exited with 1 +++ > > You can also run "capsh --print" to make sure you have all the > capabilities you expect. IIRC cap_sys_admin and cap_sys_chroot are key, > along with cap_mknod, and maybe cap_setgid and cap_setuid. I have all those. > > Also, selinux might be interfering. > That doesn't sound encouraging. Anything I should look at/for? I looked at recent entries in journalctl from around the time I ran strace but couldn't see anything interesting there either (of course, I might not know if I saw it). Martin ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2021-04-28 23:42 ` Martin Sebor @ 2021-04-28 23:54 ` DJ Delorie 2021-05-13 21:29 ` Martin Sebor 0 siblings, 1 reply; 23+ messages in thread From: DJ Delorie @ 2021-04-28 23:54 UTC (permalink / raw) To: Martin Sebor; +Cc: libc-alpha Martin Sebor <msebor@gmail.com> writes: >> (which should be bind-mounted inside your test chroot, which would be >> /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) > > /build/glibc/testroot.root/build/glibc/ is empty. Only because you're not inside the container, where the mount exists. Containers are weird ;-) > error: test-container.c:235: can't mount /ssd/src/glibc onto > /build/glibc/testroot.root/ssd/src/glibc Sigh, you have "too many permissions" :-P Again, containers are weird. You may be able to run test-container manually, but test-container itself is built against the just-built glibc >> Also, selinux might be interfering. > > That doesn't sound encouraging. Anything I should look at/for? Dunno, I typically disable selinux. Just for paranoia's sake... does all this work on a newer Fedora? ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2021-04-28 23:54 ` DJ Delorie @ 2021-05-13 21:29 ` Martin Sebor 2022-01-12 22:04 ` Martin Sebor 0 siblings, 1 reply; 23+ messages in thread From: Martin Sebor @ 2021-05-13 21:29 UTC (permalink / raw) To: DJ Delorie; +Cc: libc-alpha On 4/28/21 5:54 PM, DJ Delorie wrote: > Martin Sebor <msebor@gmail.com> writes: >>> (which should be bind-mounted inside your test chroot, which would be >>> /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) >> >> /build/glibc/testroot.root/build/glibc/ is empty. > > Only because you're not inside the container, where the mount exists. > Containers are weird ;-) > >> error: test-container.c:235: can't mount /ssd/src/glibc onto >> /build/glibc/testroot.root/ssd/src/glibc > > Sigh, you have "too many permissions" :-P Again, containers are weird. > > You may be able to run test-container manually, but test-container > itself is built against the just-built glibc > >>> Also, selinux might be interfering. >> >> That doesn't sound encouraging. Anything I should look at/for? > > Dunno, I typically disable selinux. I haven't been able to make that work yet but I also haven't tried too hard. I'll keep at it. > > Just for paranoia's sake... does all this work on a newer Fedora? Yes. I just installed F33 on my laptop and it works fine there. I haven't changed my main workstation though. It was a pain to set up. Martin ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2021-05-13 21:29 ` Martin Sebor @ 2022-01-12 22:04 ` Martin Sebor 2022-01-12 22:13 ` H.J. Lu 0 siblings, 1 reply; 23+ messages in thread From: Martin Sebor @ 2022-01-12 22:04 UTC (permalink / raw) To: DJ Delorie; +Cc: libc-alpha On 5/13/21 15:29, Martin Sebor wrote: > On 4/28/21 5:54 PM, DJ Delorie wrote: >> Martin Sebor <msebor@gmail.com> writes: >>>> (which should be bind-mounted inside your test chroot, which would be >>>> /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) >>> >>> /build/glibc/testroot.root/build/glibc/ is empty. >> >> Only because you're not inside the container, where the mount exists. >> Containers are weird ;-) >> >>> error: test-container.c:235: can't mount /ssd/src/glibc onto >>> /build/glibc/testroot.root/ssd/src/glibc >> >> Sigh, you have "too many permissions" :-P Again, containers are weird. >> >> You may be able to run test-container manually, but test-container >> itself is built against the just-built glibc >> >>>> Also, selinux might be interfering. >>> >>> That doesn't sound encouraging. Anything I should look at/for? >> >> Dunno, I typically disable selinux. > > I haven't been able to make that work yet but I also haven't tried > too hard. I'll keep at it. > >> >> Just for paranoia's sake... does all this work on a newer Fedora? > > Yes. I just installed F33 on my laptop and it works fine there. > I haven't changed my main workstation though. It was a pain to > set up. I finally bit the bullet and upgraded my workstation to Fedora 35, partly in hopes of resolving the Glibc test suite problems. I now get the failures below with the top of GCC 12 and Glibc trunk, even after disabling SELinux by running setenforce 0, as well as after permanently disabling it in /etc/selinux/config. Is there something else I should try? Thanks Martin UNSUPPORTED: assert/tst-assert-c++ UNSUPPORTED: assert/tst-assert-g++ UNSUPPORTED: debug/tst-chk4 UNSUPPORTED: debug/tst-chk5 UNSUPPORTED: debug/tst-chk6 UNSUPPORTED: debug/tst-chk8 UNSUPPORTED: debug/tst-lfschk4 UNSUPPORTED: debug/tst-lfschk5 UNSUPPORTED: debug/tst-lfschk6 UNSUPPORTED: dlfcn/bug-atexit3 UNSUPPORTED: elf/tst-audit10 UNSUPPORTED: elf/tst-avx512 FAIL: elf/tst-dlopen-self-container FAIL: elf/tst-dlopen-tlsmodid-container UNSUPPORTED: elf/tst-env-setuid UNSUPPORTED: elf/tst-env-setuid-tunables FAIL: elf/tst-glibc-hwcaps-2-cache FAIL: elf/tst-glibc-hwcaps-cache FAIL: elf/tst-glibc-hwcaps-prepend-cache XPASS: elf/tst-ifunc-isa-1 XPASS: elf/tst-ifunc-isa-1-static XPASS: elf/tst-ifunc-isa-2 XPASS: elf/tst-ifunc-isa-2-static FAIL: elf/tst-ldconfig-bad-aux-cache FAIL: elf/tst-ldconfig-ld_so_conf-update FAIL: elf/tst-pldd FAIL: elf/tst-preload-pthread-libc XPASS: elf/tst-protected1a XPASS: elf/tst-protected1b FAIL: grp/tst-initgroups1 FAIL: grp/tst-initgroups2 FAIL: locale/tst-localedef-path-norm FAIL: localedata/tst-localedef-hardlinks UNSUPPORTED: math/test-double-libmvec-acos-avx512f UNSUPPORTED: math/test-double-libmvec-acosh-avx512f UNSUPPORTED: math/test-double-libmvec-asin-avx512f UNSUPPORTED: math/test-double-libmvec-asinh-avx512f UNSUPPORTED: math/test-double-libmvec-atan-avx512f UNSUPPORTED: math/test-double-libmvec-atan2-avx512f UNSUPPORTED: math/test-double-libmvec-atanh-avx512f UNSUPPORTED: math/test-double-libmvec-cbrt-avx512f UNSUPPORTED: math/test-double-libmvec-cos-avx512f UNSUPPORTED: math/test-double-libmvec-cosh-avx512f UNSUPPORTED: math/test-double-libmvec-erf-avx512f UNSUPPORTED: math/test-double-libmvec-erfc-avx512f UNSUPPORTED: math/test-double-libmvec-exp-avx512f UNSUPPORTED: math/test-double-libmvec-exp10-avx512f UNSUPPORTED: math/test-double-libmvec-exp2-avx512f UNSUPPORTED: math/test-double-libmvec-expm1-avx512f UNSUPPORTED: math/test-double-libmvec-hypot-avx512f UNSUPPORTED: math/test-double-libmvec-log-avx512f UNSUPPORTED: math/test-double-libmvec-log10-avx512f UNSUPPORTED: math/test-double-libmvec-log1p-avx512f UNSUPPORTED: math/test-double-libmvec-log2-avx512f UNSUPPORTED: math/test-double-libmvec-pow-avx512f UNSUPPORTED: math/test-double-libmvec-sin-avx512f UNSUPPORTED: math/test-double-libmvec-sincos-avx512f UNSUPPORTED: math/test-double-libmvec-sinh-avx512f UNSUPPORTED: math/test-double-libmvec-tan-avx512f UNSUPPORTED: math/test-double-libmvec-tanh-avx512f UNSUPPORTED: math/test-float-libmvec-acosf-avx512f UNSUPPORTED: math/test-float-libmvec-acoshf-avx512f UNSUPPORTED: math/test-float-libmvec-asinf-avx512f UNSUPPORTED: math/test-float-libmvec-asinhf-avx512f UNSUPPORTED: math/test-float-libmvec-atan2f-avx512f UNSUPPORTED: math/test-float-libmvec-atanf-avx512f UNSUPPORTED: math/test-float-libmvec-atanhf-avx512f UNSUPPORTED: math/test-float-libmvec-cbrtf-avx512f UNSUPPORTED: math/test-float-libmvec-cosf-avx512f UNSUPPORTED: math/test-float-libmvec-coshf-avx512f UNSUPPORTED: math/test-float-libmvec-erfcf-avx512f UNSUPPORTED: math/test-float-libmvec-erff-avx512f UNSUPPORTED: math/test-float-libmvec-exp10f-avx512f UNSUPPORTED: math/test-float-libmvec-exp2f-avx512f UNSUPPORTED: math/test-float-libmvec-expf-avx512f UNSUPPORTED: math/test-float-libmvec-expm1f-avx512f UNSUPPORTED: math/test-float-libmvec-hypotf-avx512f UNSUPPORTED: math/test-float-libmvec-log10f-avx512f UNSUPPORTED: math/test-float-libmvec-log1pf-avx512f UNSUPPORTED: math/test-float-libmvec-log2f-avx512f UNSUPPORTED: math/test-float-libmvec-logf-avx512f UNSUPPORTED: math/test-float-libmvec-powf-avx512f UNSUPPORTED: math/test-float-libmvec-sincosf-avx512f UNSUPPORTED: math/test-float-libmvec-sinf-avx512f UNSUPPORTED: math/test-float-libmvec-sinhf-avx512f UNSUPPORTED: math/test-float-libmvec-tanf-avx512f UNSUPPORTED: math/test-float-libmvec-tanhf-avx512f UNSUPPORTED: misc/tst-adjtimex UNSUPPORTED: misc/tst-clock_adjtime UNSUPPORTED: misc/tst-ntp_adjtime UNSUPPORTED: misc/tst-pkey UNSUPPORTED: nptl/tst-cancel24 UNSUPPORTED: nptl/tst-cancel24-static UNSUPPORTED: nptl/tst-minstack-throw UNSUPPORTED: nptl/tst-once5 FAIL: nptl/tst-pthread-getattr UNSUPPORTED: nptl/tst-thread-exit-clobber UNSUPPORTED: nptl/tst-thread_local1 FAIL: nss/tst-nss-compat1 FAIL: nss/tst-nss-db-endgrent FAIL: nss/tst-nss-db-endpwent FAIL: nss/tst-nss-files-hosts-long FAIL: nss/tst-nss-test3 FAIL: nss/tst-reload1 FAIL: nss/tst-reload2 FAIL: posix/bug-ga2 UNSUPPORTED: posix/bug-ga2-mem FAIL: posix/tst-vfork3 UNSUPPORTED: posix/tst-vfork3-mem UNSUPPORTED: resolv/mtrace-tst-leaks2 FAIL: resolv/tst-leaks2 UNSUPPORTED: stdlib/tst-quick_exit UNSUPPORTED: stdlib/tst-secure-getenv FAIL: stdlib/tst-system UNSUPPORTED: stdlib/tst-thread-quick_exit UNSUPPORTED: string/tst-memchr-rtm UNSUPPORTED: string/tst-memcmp-rtm UNSUPPORTED: string/tst-memmove-rtm UNSUPPORTED: string/tst-memrchr-rtm UNSUPPORTED: string/tst-memset-rtm UNSUPPORTED: string/tst-strchr-rtm UNSUPPORTED: string/tst-strcpy-rtm FAIL: string/tst-strerror UNSUPPORTED: string/tst-strlen-rtm UNSUPPORTED: string/tst-strncmp-rtm UNSUPPORTED: string/tst-strrchr-rtm FAIL: string/tst-strsignal UNSUPPORTED: time/tst-clock_settime UNSUPPORTED: time/tst-settimeofday Summary of test results: 27 FAIL 4904 PASS 96 UNSUPPORTED 16 XFAIL 6 XPASS ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2022-01-12 22:04 ` Martin Sebor @ 2022-01-12 22:13 ` H.J. Lu 2022-01-12 23:24 ` Martin Sebor 0 siblings, 1 reply; 23+ messages in thread From: H.J. Lu @ 2022-01-12 22:13 UTC (permalink / raw) To: Martin Sebor; +Cc: DJ Delorie, GNU C Library On Wed, Jan 12, 2022 at 2:05 PM Martin Sebor via Libc-alpha <libc-alpha@sourceware.org> wrote: > > On 5/13/21 15:29, Martin Sebor wrote: > > On 4/28/21 5:54 PM, DJ Delorie wrote: > >> Martin Sebor <msebor@gmail.com> writes: > >>>> (which should be bind-mounted inside your test chroot, which would be > >>>> /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) > >>> > >>> /build/glibc/testroot.root/build/glibc/ is empty. > >> > >> Only because you're not inside the container, where the mount exists. > >> Containers are weird ;-) > >> > >>> error: test-container.c:235: can't mount /ssd/src/glibc onto > >>> /build/glibc/testroot.root/ssd/src/glibc > >> > >> Sigh, you have "too many permissions" :-P Again, containers are weird. > >> > >> You may be able to run test-container manually, but test-container > >> itself is built against the just-built glibc > >> > >>>> Also, selinux might be interfering. > >>> > >>> That doesn't sound encouraging. Anything I should look at/for? > >> > >> Dunno, I typically disable selinux. > > > > I haven't been able to make that work yet but I also haven't tried > > too hard. I'll keep at it. > > > >> > >> Just for paranoia's sake... does all this work on a newer Fedora? > > > > Yes. I just installed F33 on my laptop and it works fine there. > > I haven't changed my main workstation though. It was a pain to > > set up. > > I finally bit the bullet and upgraded my workstation to Fedora > 35, partly in hopes of resolving the Glibc test suite problems. > I now get the failures below with the top of GCC 12 and Glibc > trunk, even after disabling SELinux by running setenforce 0, > as well as after permanently disabling it in /etc/selinux/config. > Is there something else I should try? > > Thanks > Martin > > UNSUPPORTED: assert/tst-assert-c++ > UNSUPPORTED: assert/tst-assert-g++ > UNSUPPORTED: debug/tst-chk4 > UNSUPPORTED: debug/tst-chk5 > UNSUPPORTED: debug/tst-chk6 > UNSUPPORTED: debug/tst-chk8 > UNSUPPORTED: debug/tst-lfschk4 > UNSUPPORTED: debug/tst-lfschk5 > UNSUPPORTED: debug/tst-lfschk6 > UNSUPPORTED: dlfcn/bug-atexit3 > UNSUPPORTED: elf/tst-audit10 > UNSUPPORTED: elf/tst-avx512 > FAIL: elf/tst-dlopen-self-container > FAIL: elf/tst-dlopen-tlsmodid-container > UNSUPPORTED: elf/tst-env-setuid > UNSUPPORTED: elf/tst-env-setuid-tunables > FAIL: elf/tst-glibc-hwcaps-2-cache > FAIL: elf/tst-glibc-hwcaps-cache > FAIL: elf/tst-glibc-hwcaps-prepend-cache > XPASS: elf/tst-ifunc-isa-1 > XPASS: elf/tst-ifunc-isa-1-static > XPASS: elf/tst-ifunc-isa-2 > XPASS: elf/tst-ifunc-isa-2-static > FAIL: elf/tst-ldconfig-bad-aux-cache > FAIL: elf/tst-ldconfig-ld_so_conf-update > FAIL: elf/tst-pldd > FAIL: elf/tst-preload-pthread-libc > XPASS: elf/tst-protected1a > XPASS: elf/tst-protected1b > FAIL: grp/tst-initgroups1 > FAIL: grp/tst-initgroups2 > FAIL: locale/tst-localedef-path-norm > FAIL: localedata/tst-localedef-hardlinks > UNSUPPORTED: math/test-double-libmvec-acos-avx512f > UNSUPPORTED: math/test-double-libmvec-acosh-avx512f > UNSUPPORTED: math/test-double-libmvec-asin-avx512f > UNSUPPORTED: math/test-double-libmvec-asinh-avx512f > UNSUPPORTED: math/test-double-libmvec-atan-avx512f > UNSUPPORTED: math/test-double-libmvec-atan2-avx512f > UNSUPPORTED: math/test-double-libmvec-atanh-avx512f > UNSUPPORTED: math/test-double-libmvec-cbrt-avx512f > UNSUPPORTED: math/test-double-libmvec-cos-avx512f > UNSUPPORTED: math/test-double-libmvec-cosh-avx512f > UNSUPPORTED: math/test-double-libmvec-erf-avx512f > UNSUPPORTED: math/test-double-libmvec-erfc-avx512f > UNSUPPORTED: math/test-double-libmvec-exp-avx512f > UNSUPPORTED: math/test-double-libmvec-exp10-avx512f > UNSUPPORTED: math/test-double-libmvec-exp2-avx512f > UNSUPPORTED: math/test-double-libmvec-expm1-avx512f > UNSUPPORTED: math/test-double-libmvec-hypot-avx512f > UNSUPPORTED: math/test-double-libmvec-log-avx512f > UNSUPPORTED: math/test-double-libmvec-log10-avx512f > UNSUPPORTED: math/test-double-libmvec-log1p-avx512f > UNSUPPORTED: math/test-double-libmvec-log2-avx512f > UNSUPPORTED: math/test-double-libmvec-pow-avx512f > UNSUPPORTED: math/test-double-libmvec-sin-avx512f > UNSUPPORTED: math/test-double-libmvec-sincos-avx512f > UNSUPPORTED: math/test-double-libmvec-sinh-avx512f > UNSUPPORTED: math/test-double-libmvec-tan-avx512f > UNSUPPORTED: math/test-double-libmvec-tanh-avx512f > UNSUPPORTED: math/test-float-libmvec-acosf-avx512f > UNSUPPORTED: math/test-float-libmvec-acoshf-avx512f > UNSUPPORTED: math/test-float-libmvec-asinf-avx512f > UNSUPPORTED: math/test-float-libmvec-asinhf-avx512f > UNSUPPORTED: math/test-float-libmvec-atan2f-avx512f > UNSUPPORTED: math/test-float-libmvec-atanf-avx512f > UNSUPPORTED: math/test-float-libmvec-atanhf-avx512f > UNSUPPORTED: math/test-float-libmvec-cbrtf-avx512f > UNSUPPORTED: math/test-float-libmvec-cosf-avx512f > UNSUPPORTED: math/test-float-libmvec-coshf-avx512f > UNSUPPORTED: math/test-float-libmvec-erfcf-avx512f > UNSUPPORTED: math/test-float-libmvec-erff-avx512f > UNSUPPORTED: math/test-float-libmvec-exp10f-avx512f > UNSUPPORTED: math/test-float-libmvec-exp2f-avx512f > UNSUPPORTED: math/test-float-libmvec-expf-avx512f > UNSUPPORTED: math/test-float-libmvec-expm1f-avx512f > UNSUPPORTED: math/test-float-libmvec-hypotf-avx512f > UNSUPPORTED: math/test-float-libmvec-log10f-avx512f > UNSUPPORTED: math/test-float-libmvec-log1pf-avx512f > UNSUPPORTED: math/test-float-libmvec-log2f-avx512f > UNSUPPORTED: math/test-float-libmvec-logf-avx512f > UNSUPPORTED: math/test-float-libmvec-powf-avx512f > UNSUPPORTED: math/test-float-libmvec-sincosf-avx512f > UNSUPPORTED: math/test-float-libmvec-sinf-avx512f > UNSUPPORTED: math/test-float-libmvec-sinhf-avx512f > UNSUPPORTED: math/test-float-libmvec-tanf-avx512f > UNSUPPORTED: math/test-float-libmvec-tanhf-avx512f > UNSUPPORTED: misc/tst-adjtimex > UNSUPPORTED: misc/tst-clock_adjtime > UNSUPPORTED: misc/tst-ntp_adjtime > UNSUPPORTED: misc/tst-pkey > UNSUPPORTED: nptl/tst-cancel24 > UNSUPPORTED: nptl/tst-cancel24-static > UNSUPPORTED: nptl/tst-minstack-throw > UNSUPPORTED: nptl/tst-once5 > FAIL: nptl/tst-pthread-getattr > UNSUPPORTED: nptl/tst-thread-exit-clobber > UNSUPPORTED: nptl/tst-thread_local1 > FAIL: nss/tst-nss-compat1 > FAIL: nss/tst-nss-db-endgrent > FAIL: nss/tst-nss-db-endpwent > FAIL: nss/tst-nss-files-hosts-long > FAIL: nss/tst-nss-test3 > FAIL: nss/tst-reload1 > FAIL: nss/tst-reload2 > FAIL: posix/bug-ga2 > UNSUPPORTED: posix/bug-ga2-mem > FAIL: posix/tst-vfork3 > UNSUPPORTED: posix/tst-vfork3-mem > UNSUPPORTED: resolv/mtrace-tst-leaks2 > FAIL: resolv/tst-leaks2 > UNSUPPORTED: stdlib/tst-quick_exit > UNSUPPORTED: stdlib/tst-secure-getenv > FAIL: stdlib/tst-system > UNSUPPORTED: stdlib/tst-thread-quick_exit > UNSUPPORTED: string/tst-memchr-rtm > UNSUPPORTED: string/tst-memcmp-rtm > UNSUPPORTED: string/tst-memmove-rtm > UNSUPPORTED: string/tst-memrchr-rtm > UNSUPPORTED: string/tst-memset-rtm > UNSUPPORTED: string/tst-strchr-rtm > UNSUPPORTED: string/tst-strcpy-rtm > FAIL: string/tst-strerror > UNSUPPORTED: string/tst-strlen-rtm > UNSUPPORTED: string/tst-strncmp-rtm > UNSUPPORTED: string/tst-strrchr-rtm > FAIL: string/tst-strsignal > UNSUPPORTED: time/tst-clock_settime > UNSUPPORTED: time/tst-settimeofday > Summary of test results: > 27 FAIL > 4904 PASS > 96 UNSUPPORTED > 16 XFAIL > 6 XPASS See: https://sourceware.org/bugzilla/show_bug.cgi?id=28455 My last patch is at https://patchwork.sourceware.org/project/glibc/patch/20220104140009.1578867-1-hjl.tools@gmail.com/ -- H.J. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2022-01-12 22:13 ` H.J. Lu @ 2022-01-12 23:24 ` Martin Sebor 2022-01-14 23:51 ` Martin Sebor 0 siblings, 1 reply; 23+ messages in thread From: Martin Sebor @ 2022-01-12 23:24 UTC (permalink / raw) To: H.J. Lu; +Cc: DJ Delorie, GNU C Library On 1/12/22 15:13, H.J. Lu wrote: > On Wed, Jan 12, 2022 at 2:05 PM Martin Sebor via Libc-alpha > <libc-alpha@sourceware.org> wrote: >> >> On 5/13/21 15:29, Martin Sebor wrote: >>> On 4/28/21 5:54 PM, DJ Delorie wrote: >>>> Martin Sebor <msebor@gmail.com> writes: >>>>>> (which should be bind-mounted inside your test chroot, which would be >>>>>> /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) >>>>> >>>>> /build/glibc/testroot.root/build/glibc/ is empty. >>>> >>>> Only because you're not inside the container, where the mount exists. >>>> Containers are weird ;-) >>>> >>>>> error: test-container.c:235: can't mount /ssd/src/glibc onto >>>>> /build/glibc/testroot.root/ssd/src/glibc >>>> >>>> Sigh, you have "too many permissions" :-P Again, containers are weird. >>>> >>>> You may be able to run test-container manually, but test-container >>>> itself is built against the just-built glibc >>>> >>>>>> Also, selinux might be interfering. >>>>> >>>>> That doesn't sound encouraging. Anything I should look at/for? >>>> >>>> Dunno, I typically disable selinux. >>> >>> I haven't been able to make that work yet but I also haven't tried >>> too hard. I'll keep at it. >>> >>>> >>>> Just for paranoia's sake... does all this work on a newer Fedora? >>> >>> Yes. I just installed F33 on my laptop and it works fine there. >>> I haven't changed my main workstation though. It was a pain to >>> set up. >> >> I finally bit the bullet and upgraded my workstation to Fedora >> 35, partly in hopes of resolving the Glibc test suite problems. >> I now get the failures below with the top of GCC 12 and Glibc >> trunk, even after disabling SELinux by running setenforce 0, >> as well as after permanently disabling it in /etc/selinux/config. >> Is there something else I should try? >> >> Thanks >> Martin >> >> UNSUPPORTED: assert/tst-assert-c++ >> UNSUPPORTED: assert/tst-assert-g++ >> UNSUPPORTED: debug/tst-chk4 >> UNSUPPORTED: debug/tst-chk5 >> UNSUPPORTED: debug/tst-chk6 >> UNSUPPORTED: debug/tst-chk8 >> UNSUPPORTED: debug/tst-lfschk4 >> UNSUPPORTED: debug/tst-lfschk5 >> UNSUPPORTED: debug/tst-lfschk6 >> UNSUPPORTED: dlfcn/bug-atexit3 >> UNSUPPORTED: elf/tst-audit10 >> UNSUPPORTED: elf/tst-avx512 >> FAIL: elf/tst-dlopen-self-container >> FAIL: elf/tst-dlopen-tlsmodid-container >> UNSUPPORTED: elf/tst-env-setuid >> UNSUPPORTED: elf/tst-env-setuid-tunables >> FAIL: elf/tst-glibc-hwcaps-2-cache >> FAIL: elf/tst-glibc-hwcaps-cache >> FAIL: elf/tst-glibc-hwcaps-prepend-cache >> XPASS: elf/tst-ifunc-isa-1 >> XPASS: elf/tst-ifunc-isa-1-static >> XPASS: elf/tst-ifunc-isa-2 >> XPASS: elf/tst-ifunc-isa-2-static >> FAIL: elf/tst-ldconfig-bad-aux-cache >> FAIL: elf/tst-ldconfig-ld_so_conf-update >> FAIL: elf/tst-pldd >> FAIL: elf/tst-preload-pthread-libc >> XPASS: elf/tst-protected1a >> XPASS: elf/tst-protected1b >> FAIL: grp/tst-initgroups1 >> FAIL: grp/tst-initgroups2 >> FAIL: locale/tst-localedef-path-norm >> FAIL: localedata/tst-localedef-hardlinks >> UNSUPPORTED: math/test-double-libmvec-acos-avx512f >> UNSUPPORTED: math/test-double-libmvec-acosh-avx512f >> UNSUPPORTED: math/test-double-libmvec-asin-avx512f >> UNSUPPORTED: math/test-double-libmvec-asinh-avx512f >> UNSUPPORTED: math/test-double-libmvec-atan-avx512f >> UNSUPPORTED: math/test-double-libmvec-atan2-avx512f >> UNSUPPORTED: math/test-double-libmvec-atanh-avx512f >> UNSUPPORTED: math/test-double-libmvec-cbrt-avx512f >> UNSUPPORTED: math/test-double-libmvec-cos-avx512f >> UNSUPPORTED: math/test-double-libmvec-cosh-avx512f >> UNSUPPORTED: math/test-double-libmvec-erf-avx512f >> UNSUPPORTED: math/test-double-libmvec-erfc-avx512f >> UNSUPPORTED: math/test-double-libmvec-exp-avx512f >> UNSUPPORTED: math/test-double-libmvec-exp10-avx512f >> UNSUPPORTED: math/test-double-libmvec-exp2-avx512f >> UNSUPPORTED: math/test-double-libmvec-expm1-avx512f >> UNSUPPORTED: math/test-double-libmvec-hypot-avx512f >> UNSUPPORTED: math/test-double-libmvec-log-avx512f >> UNSUPPORTED: math/test-double-libmvec-log10-avx512f >> UNSUPPORTED: math/test-double-libmvec-log1p-avx512f >> UNSUPPORTED: math/test-double-libmvec-log2-avx512f >> UNSUPPORTED: math/test-double-libmvec-pow-avx512f >> UNSUPPORTED: math/test-double-libmvec-sin-avx512f >> UNSUPPORTED: math/test-double-libmvec-sincos-avx512f >> UNSUPPORTED: math/test-double-libmvec-sinh-avx512f >> UNSUPPORTED: math/test-double-libmvec-tan-avx512f >> UNSUPPORTED: math/test-double-libmvec-tanh-avx512f >> UNSUPPORTED: math/test-float-libmvec-acosf-avx512f >> UNSUPPORTED: math/test-float-libmvec-acoshf-avx512f >> UNSUPPORTED: math/test-float-libmvec-asinf-avx512f >> UNSUPPORTED: math/test-float-libmvec-asinhf-avx512f >> UNSUPPORTED: math/test-float-libmvec-atan2f-avx512f >> UNSUPPORTED: math/test-float-libmvec-atanf-avx512f >> UNSUPPORTED: math/test-float-libmvec-atanhf-avx512f >> UNSUPPORTED: math/test-float-libmvec-cbrtf-avx512f >> UNSUPPORTED: math/test-float-libmvec-cosf-avx512f >> UNSUPPORTED: math/test-float-libmvec-coshf-avx512f >> UNSUPPORTED: math/test-float-libmvec-erfcf-avx512f >> UNSUPPORTED: math/test-float-libmvec-erff-avx512f >> UNSUPPORTED: math/test-float-libmvec-exp10f-avx512f >> UNSUPPORTED: math/test-float-libmvec-exp2f-avx512f >> UNSUPPORTED: math/test-float-libmvec-expf-avx512f >> UNSUPPORTED: math/test-float-libmvec-expm1f-avx512f >> UNSUPPORTED: math/test-float-libmvec-hypotf-avx512f >> UNSUPPORTED: math/test-float-libmvec-log10f-avx512f >> UNSUPPORTED: math/test-float-libmvec-log1pf-avx512f >> UNSUPPORTED: math/test-float-libmvec-log2f-avx512f >> UNSUPPORTED: math/test-float-libmvec-logf-avx512f >> UNSUPPORTED: math/test-float-libmvec-powf-avx512f >> UNSUPPORTED: math/test-float-libmvec-sincosf-avx512f >> UNSUPPORTED: math/test-float-libmvec-sinf-avx512f >> UNSUPPORTED: math/test-float-libmvec-sinhf-avx512f >> UNSUPPORTED: math/test-float-libmvec-tanf-avx512f >> UNSUPPORTED: math/test-float-libmvec-tanhf-avx512f >> UNSUPPORTED: misc/tst-adjtimex >> UNSUPPORTED: misc/tst-clock_adjtime >> UNSUPPORTED: misc/tst-ntp_adjtime >> UNSUPPORTED: misc/tst-pkey >> UNSUPPORTED: nptl/tst-cancel24 >> UNSUPPORTED: nptl/tst-cancel24-static >> UNSUPPORTED: nptl/tst-minstack-throw >> UNSUPPORTED: nptl/tst-once5 >> FAIL: nptl/tst-pthread-getattr >> UNSUPPORTED: nptl/tst-thread-exit-clobber >> UNSUPPORTED: nptl/tst-thread_local1 >> FAIL: nss/tst-nss-compat1 >> FAIL: nss/tst-nss-db-endgrent >> FAIL: nss/tst-nss-db-endpwent >> FAIL: nss/tst-nss-files-hosts-long >> FAIL: nss/tst-nss-test3 >> FAIL: nss/tst-reload1 >> FAIL: nss/tst-reload2 >> FAIL: posix/bug-ga2 >> UNSUPPORTED: posix/bug-ga2-mem >> FAIL: posix/tst-vfork3 >> UNSUPPORTED: posix/tst-vfork3-mem >> UNSUPPORTED: resolv/mtrace-tst-leaks2 >> FAIL: resolv/tst-leaks2 >> UNSUPPORTED: stdlib/tst-quick_exit >> UNSUPPORTED: stdlib/tst-secure-getenv >> FAIL: stdlib/tst-system >> UNSUPPORTED: stdlib/tst-thread-quick_exit >> UNSUPPORTED: string/tst-memchr-rtm >> UNSUPPORTED: string/tst-memcmp-rtm >> UNSUPPORTED: string/tst-memmove-rtm >> UNSUPPORTED: string/tst-memrchr-rtm >> UNSUPPORTED: string/tst-memset-rtm >> UNSUPPORTED: string/tst-strchr-rtm >> UNSUPPORTED: string/tst-strcpy-rtm >> FAIL: string/tst-strerror >> UNSUPPORTED: string/tst-strlen-rtm >> UNSUPPORTED: string/tst-strncmp-rtm >> UNSUPPORTED: string/tst-strrchr-rtm >> FAIL: string/tst-strsignal >> UNSUPPORTED: time/tst-clock_settime >> UNSUPPORTED: time/tst-settimeofday >> Summary of test results: >> 27 FAIL >> 4904 PASS >> 96 UNSUPPORTED >> 16 XFAIL >> 6 XPASS > > See: > > https://sourceware.org/bugzilla/show_bug.cgi?id=28455 > > My last patch is at > > https://patchwork.sourceware.org/project/glibc/patch/20220104140009.1578867-1-hjl.tools@gmail.com/ Thanks, but I still get the same results even with the patch applied and after rebuilding everything. The new test added by the patch, elf/tst-global2, passes. Am I missing something else or is this still some container problem? Martin ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2022-01-12 23:24 ` Martin Sebor @ 2022-01-14 23:51 ` Martin Sebor 2022-01-17 18:04 ` Adhemerval Zanella 0 siblings, 1 reply; 23+ messages in thread From: Martin Sebor @ 2022-01-14 23:51 UTC (permalink / raw) To: H.J. Lu; +Cc: DJ Delorie, GNU C Library On 1/12/22 16:24, Martin Sebor wrote: > On 1/12/22 15:13, H.J. Lu wrote: >> On Wed, Jan 12, 2022 at 2:05 PM Martin Sebor via Libc-alpha >> <libc-alpha@sourceware.org> wrote: >>> >>> On 5/13/21 15:29, Martin Sebor wrote: >>>> On 4/28/21 5:54 PM, DJ Delorie wrote: >>>>> Martin Sebor <msebor@gmail.com> writes: >>>>>>> (which should be bind-mounted inside your test chroot, which >>>>>>> would be >>>>>>> /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) >>>>>> >>>>>> /build/glibc/testroot.root/build/glibc/ is empty. >>>>> >>>>> Only because you're not inside the container, where the mount exists. >>>>> Containers are weird ;-) >>>>> >>>>>> error: test-container.c:235: can't mount /ssd/src/glibc onto >>>>>> /build/glibc/testroot.root/ssd/src/glibc >>>>> >>>>> Sigh, you have "too many permissions" :-P Again, containers are >>>>> weird. >>>>> >>>>> You may be able to run test-container manually, but test-container >>>>> itself is built against the just-built glibc >>>>> >>>>>>> Also, selinux might be interfering. >>>>>> >>>>>> That doesn't sound encouraging. Anything I should look at/for? >>>>> >>>>> Dunno, I typically disable selinux. >>>> >>>> I haven't been able to make that work yet but I also haven't tried >>>> too hard. I'll keep at it. >>>> >>>>> >>>>> Just for paranoia's sake... does all this work on a newer Fedora? >>>> >>>> Yes. I just installed F33 on my laptop and it works fine there. >>>> I haven't changed my main workstation though. It was a pain to >>>> set up. >>> >>> I finally bit the bullet and upgraded my workstation to Fedora >>> 35, partly in hopes of resolving the Glibc test suite problems. >>> I now get the failures below with the top of GCC 12 and Glibc >>> trunk, even after disabling SELinux by running setenforce 0, >>> as well as after permanently disabling it in /etc/selinux/config. >>> Is there something else I should try? >>> >>> Thanks >>> Martin >>> >>> UNSUPPORTED: assert/tst-assert-c++ >>> UNSUPPORTED: assert/tst-assert-g++ >>> UNSUPPORTED: debug/tst-chk4 >>> UNSUPPORTED: debug/tst-chk5 >>> UNSUPPORTED: debug/tst-chk6 >>> UNSUPPORTED: debug/tst-chk8 >>> UNSUPPORTED: debug/tst-lfschk4 >>> UNSUPPORTED: debug/tst-lfschk5 >>> UNSUPPORTED: debug/tst-lfschk6 >>> UNSUPPORTED: dlfcn/bug-atexit3 >>> UNSUPPORTED: elf/tst-audit10 >>> UNSUPPORTED: elf/tst-avx512 >>> FAIL: elf/tst-dlopen-self-container >>> FAIL: elf/tst-dlopen-tlsmodid-container >>> UNSUPPORTED: elf/tst-env-setuid >>> UNSUPPORTED: elf/tst-env-setuid-tunables >>> FAIL: elf/tst-glibc-hwcaps-2-cache >>> FAIL: elf/tst-glibc-hwcaps-cache >>> FAIL: elf/tst-glibc-hwcaps-prepend-cache >>> XPASS: elf/tst-ifunc-isa-1 >>> XPASS: elf/tst-ifunc-isa-1-static >>> XPASS: elf/tst-ifunc-isa-2 >>> XPASS: elf/tst-ifunc-isa-2-static >>> FAIL: elf/tst-ldconfig-bad-aux-cache >>> FAIL: elf/tst-ldconfig-ld_so_conf-update >>> FAIL: elf/tst-pldd >>> FAIL: elf/tst-preload-pthread-libc >>> XPASS: elf/tst-protected1a >>> XPASS: elf/tst-protected1b >>> FAIL: grp/tst-initgroups1 >>> FAIL: grp/tst-initgroups2 >>> FAIL: locale/tst-localedef-path-norm >>> FAIL: localedata/tst-localedef-hardlinks >>> UNSUPPORTED: math/test-double-libmvec-acos-avx512f >>> UNSUPPORTED: math/test-double-libmvec-acosh-avx512f >>> UNSUPPORTED: math/test-double-libmvec-asin-avx512f >>> UNSUPPORTED: math/test-double-libmvec-asinh-avx512f >>> UNSUPPORTED: math/test-double-libmvec-atan-avx512f >>> UNSUPPORTED: math/test-double-libmvec-atan2-avx512f >>> UNSUPPORTED: math/test-double-libmvec-atanh-avx512f >>> UNSUPPORTED: math/test-double-libmvec-cbrt-avx512f >>> UNSUPPORTED: math/test-double-libmvec-cos-avx512f >>> UNSUPPORTED: math/test-double-libmvec-cosh-avx512f >>> UNSUPPORTED: math/test-double-libmvec-erf-avx512f >>> UNSUPPORTED: math/test-double-libmvec-erfc-avx512f >>> UNSUPPORTED: math/test-double-libmvec-exp-avx512f >>> UNSUPPORTED: math/test-double-libmvec-exp10-avx512f >>> UNSUPPORTED: math/test-double-libmvec-exp2-avx512f >>> UNSUPPORTED: math/test-double-libmvec-expm1-avx512f >>> UNSUPPORTED: math/test-double-libmvec-hypot-avx512f >>> UNSUPPORTED: math/test-double-libmvec-log-avx512f >>> UNSUPPORTED: math/test-double-libmvec-log10-avx512f >>> UNSUPPORTED: math/test-double-libmvec-log1p-avx512f >>> UNSUPPORTED: math/test-double-libmvec-log2-avx512f >>> UNSUPPORTED: math/test-double-libmvec-pow-avx512f >>> UNSUPPORTED: math/test-double-libmvec-sin-avx512f >>> UNSUPPORTED: math/test-double-libmvec-sincos-avx512f >>> UNSUPPORTED: math/test-double-libmvec-sinh-avx512f >>> UNSUPPORTED: math/test-double-libmvec-tan-avx512f >>> UNSUPPORTED: math/test-double-libmvec-tanh-avx512f >>> UNSUPPORTED: math/test-float-libmvec-acosf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-acoshf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-asinf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-asinhf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-atan2f-avx512f >>> UNSUPPORTED: math/test-float-libmvec-atanf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-atanhf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-cbrtf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-cosf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-coshf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-erfcf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-erff-avx512f >>> UNSUPPORTED: math/test-float-libmvec-exp10f-avx512f >>> UNSUPPORTED: math/test-float-libmvec-exp2f-avx512f >>> UNSUPPORTED: math/test-float-libmvec-expf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-expm1f-avx512f >>> UNSUPPORTED: math/test-float-libmvec-hypotf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-log10f-avx512f >>> UNSUPPORTED: math/test-float-libmvec-log1pf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-log2f-avx512f >>> UNSUPPORTED: math/test-float-libmvec-logf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-powf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-sincosf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-sinf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-sinhf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-tanf-avx512f >>> UNSUPPORTED: math/test-float-libmvec-tanhf-avx512f >>> UNSUPPORTED: misc/tst-adjtimex >>> UNSUPPORTED: misc/tst-clock_adjtime >>> UNSUPPORTED: misc/tst-ntp_adjtime >>> UNSUPPORTED: misc/tst-pkey >>> UNSUPPORTED: nptl/tst-cancel24 >>> UNSUPPORTED: nptl/tst-cancel24-static >>> UNSUPPORTED: nptl/tst-minstack-throw >>> UNSUPPORTED: nptl/tst-once5 >>> FAIL: nptl/tst-pthread-getattr >>> UNSUPPORTED: nptl/tst-thread-exit-clobber >>> UNSUPPORTED: nptl/tst-thread_local1 >>> FAIL: nss/tst-nss-compat1 >>> FAIL: nss/tst-nss-db-endgrent >>> FAIL: nss/tst-nss-db-endpwent >>> FAIL: nss/tst-nss-files-hosts-long >>> FAIL: nss/tst-nss-test3 >>> FAIL: nss/tst-reload1 >>> FAIL: nss/tst-reload2 >>> FAIL: posix/bug-ga2 >>> UNSUPPORTED: posix/bug-ga2-mem >>> FAIL: posix/tst-vfork3 >>> UNSUPPORTED: posix/tst-vfork3-mem >>> UNSUPPORTED: resolv/mtrace-tst-leaks2 >>> FAIL: resolv/tst-leaks2 >>> UNSUPPORTED: stdlib/tst-quick_exit >>> UNSUPPORTED: stdlib/tst-secure-getenv >>> FAIL: stdlib/tst-system >>> UNSUPPORTED: stdlib/tst-thread-quick_exit >>> UNSUPPORTED: string/tst-memchr-rtm >>> UNSUPPORTED: string/tst-memcmp-rtm >>> UNSUPPORTED: string/tst-memmove-rtm >>> UNSUPPORTED: string/tst-memrchr-rtm >>> UNSUPPORTED: string/tst-memset-rtm >>> UNSUPPORTED: string/tst-strchr-rtm >>> UNSUPPORTED: string/tst-strcpy-rtm >>> FAIL: string/tst-strerror >>> UNSUPPORTED: string/tst-strlen-rtm >>> UNSUPPORTED: string/tst-strncmp-rtm >>> UNSUPPORTED: string/tst-strrchr-rtm >>> FAIL: string/tst-strsignal >>> UNSUPPORTED: time/tst-clock_settime >>> UNSUPPORTED: time/tst-settimeofday >>> Summary of test results: >>> 27 FAIL >>> 4904 PASS >>> 96 UNSUPPORTED >>> 16 XFAIL >>> 6 XPASS >> >> See: >> >> https://sourceware.org/bugzilla/show_bug.cgi?id=28455 >> >> My last patch is at >> >> https://patchwork.sourceware.org/project/glibc/patch/20220104140009.1578867-1-hjl.tools@gmail.com/ >> > Thanks, but I still get the same results even with the patch > applied and after rebuilding everything. The new test added > by the patch, elf/tst-global2, passes. Am I missing something > else or is this still some container problem? The filesystem I'm using is mounted with these flags: rw,nosuid,nodev,relatime,x-gvfs-show On a hunch I tried a different filesystem, one with these flags: rw,relatime That changes things, making me wonder if one of the bits (nosuid?) might be interfering with the container magic? I still don't get a clean build on the other filesystem, but I see no failures, only unsupported results (below). The exit status of all those I checked is 77. Are these results expected? Martin UNSUPPORTED: assert/tst-assert-c++ UNSUPPORTED: assert/tst-assert-g++ UNSUPPORTED: debug/tst-fortify-cc-default-1 UNSUPPORTED: debug/tst-fortify-cc-default-2 UNSUPPORTED: debug/tst-fortify-cc-default-3 UNSUPPORTED: debug/tst-fortify-cc-lfs-1 UNSUPPORTED: debug/tst-fortify-cc-lfs-2 UNSUPPORTED: debug/tst-fortify-cc-lfs-3 UNSUPPORTED: debug/tst-fortify-cc-nongnu-1 UNSUPPORTED: debug/tst-fortify-cc-nongnu-2 UNSUPPORTED: debug/tst-fortify-cc-nongnu-3 UNSUPPORTED: dlfcn/bug-atexit3 UNSUPPORTED: elf/tst-audit10 UNSUPPORTED: elf/tst-avx512 UNSUPPORTED: elf/tst-env-setuid UNSUPPORTED: elf/tst-env-setuid-tunables XPASS: elf/tst-ifunc-isa-1 XPASS: elf/tst-ifunc-isa-1-static XPASS: elf/tst-ifunc-isa-2 XPASS: elf/tst-ifunc-isa-2-static XPASS: elf/tst-protected1a XPASS: elf/tst-protected1b UNSUPPORTED: math/test-double-libmvec-acos-avx512f UNSUPPORTED: math/test-double-libmvec-acosh-avx512f UNSUPPORTED: math/test-double-libmvec-asin-avx512f UNSUPPORTED: math/test-double-libmvec-asinh-avx512f UNSUPPORTED: math/test-double-libmvec-atan-avx512f UNSUPPORTED: math/test-double-libmvec-atan2-avx512f UNSUPPORTED: math/test-double-libmvec-atanh-avx512f UNSUPPORTED: math/test-double-libmvec-cbrt-avx512f UNSUPPORTED: math/test-double-libmvec-cos-avx512f UNSUPPORTED: math/test-double-libmvec-cosh-avx512f UNSUPPORTED: math/test-double-libmvec-erf-avx512f UNSUPPORTED: math/test-double-libmvec-erfc-avx512f UNSUPPORTED: math/test-double-libmvec-exp-avx512f UNSUPPORTED: math/test-double-libmvec-exp10-avx512f UNSUPPORTED: math/test-double-libmvec-exp2-avx512f UNSUPPORTED: math/test-double-libmvec-expm1-avx512f UNSUPPORTED: math/test-double-libmvec-hypot-avx512f UNSUPPORTED: math/test-double-libmvec-log-avx512f UNSUPPORTED: math/test-double-libmvec-log10-avx512f UNSUPPORTED: math/test-double-libmvec-log1p-avx512f UNSUPPORTED: math/test-double-libmvec-log2-avx512f UNSUPPORTED: math/test-double-libmvec-pow-avx512f UNSUPPORTED: math/test-double-libmvec-sin-avx512f UNSUPPORTED: math/test-double-libmvec-sincos-avx512f UNSUPPORTED: math/test-double-libmvec-sinh-avx512f UNSUPPORTED: math/test-double-libmvec-tan-avx512f UNSUPPORTED: math/test-double-libmvec-tanh-avx512f UNSUPPORTED: math/test-float-libmvec-acosf-avx512f UNSUPPORTED: math/test-float-libmvec-acoshf-avx512f UNSUPPORTED: math/test-float-libmvec-asinf-avx512f UNSUPPORTED: math/test-float-libmvec-asinhf-avx512f UNSUPPORTED: math/test-float-libmvec-atan2f-avx512f UNSUPPORTED: math/test-float-libmvec-atanf-avx512f UNSUPPORTED: math/test-float-libmvec-atanhf-avx512f UNSUPPORTED: math/test-float-libmvec-cbrtf-avx512f UNSUPPORTED: math/test-float-libmvec-cosf-avx512f UNSUPPORTED: math/test-float-libmvec-coshf-avx512f UNSUPPORTED: math/test-float-libmvec-erfcf-avx512f UNSUPPORTED: math/test-float-libmvec-erff-avx512f UNSUPPORTED: math/test-float-libmvec-exp10f-avx512f UNSUPPORTED: math/test-float-libmvec-exp2f-avx512f UNSUPPORTED: math/test-float-libmvec-expf-avx512f UNSUPPORTED: math/test-float-libmvec-expm1f-avx512f UNSUPPORTED: math/test-float-libmvec-hypotf-avx512f UNSUPPORTED: math/test-float-libmvec-log10f-avx512f UNSUPPORTED: math/test-float-libmvec-log1pf-avx512f UNSUPPORTED: math/test-float-libmvec-log2f-avx512f UNSUPPORTED: math/test-float-libmvec-logf-avx512f UNSUPPORTED: math/test-float-libmvec-powf-avx512f UNSUPPORTED: math/test-float-libmvec-sincosf-avx512f UNSUPPORTED: math/test-float-libmvec-sinf-avx512f UNSUPPORTED: math/test-float-libmvec-sinhf-avx512f UNSUPPORTED: math/test-float-libmvec-tanf-avx512f UNSUPPORTED: math/test-float-libmvec-tanhf-avx512f UNSUPPORTED: misc/tst-adjtimex UNSUPPORTED: misc/tst-clock_adjtime UNSUPPORTED: misc/tst-ntp_adjtime UNSUPPORTED: misc/tst-pkey UNSUPPORTED: nptl/tst-cancel24 UNSUPPORTED: nptl/tst-cancel24-static UNSUPPORTED: nptl/tst-minstack-throw UNSUPPORTED: nptl/tst-once5 UNSUPPORTED: nptl/tst-thread-exit-clobber UNSUPPORTED: nptl/tst-thread_local1 UNSUPPORTED: stdlib/tst-quick_exit UNSUPPORTED: stdlib/tst-secure-getenv UNSUPPORTED: stdlib/tst-thread-quick_exit UNSUPPORTED: string/tst-memchr-rtm UNSUPPORTED: string/tst-memcmp-rtm UNSUPPORTED: string/tst-memmove-rtm UNSUPPORTED: string/tst-memrchr-rtm UNSUPPORTED: string/tst-memset-rtm UNSUPPORTED: string/tst-strchr-rtm UNSUPPORTED: string/tst-strcpy-rtm UNSUPPORTED: string/tst-strlen-rtm UNSUPPORTED: string/tst-strncmp-rtm UNSUPPORTED: string/tst-strrchr-rtm UNSUPPORTED: time/tst-clock_settime UNSUPPORTED: time/tst-settimeofday Summary of test results: 4937 PASS 95 UNSUPPORTED 16 XFAIL 6 XPASS ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2022-01-14 23:51 ` Martin Sebor @ 2022-01-17 18:04 ` Adhemerval Zanella 2022-01-17 19:09 ` Joseph Myers 2022-01-20 22:23 ` Martin Sebor 0 siblings, 2 replies; 23+ messages in thread From: Adhemerval Zanella @ 2022-01-17 18:04 UTC (permalink / raw) To: Martin Sebor, H.J. Lu; +Cc: GNU C Library On 14/01/2022 20:51, Martin Sebor via Libc-alpha wrote: > On 1/12/22 16:24, Martin Sebor wrote: >> On 1/12/22 15:13, H.J. Lu wrote: >>> On Wed, Jan 12, 2022 at 2:05 PM Martin Sebor via Libc-alpha >>> <libc-alpha@sourceware.org> wrote: >>>> >>>> On 5/13/21 15:29, Martin Sebor wrote: >>>>> On 4/28/21 5:54 PM, DJ Delorie wrote: >>>>>> Martin Sebor <msebor@gmail.com> writes: >>>>>>>> (which should be bind-mounted inside your test chroot, which would be >>>>>>>> /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) >>>>>>> >>>>>>> /build/glibc/testroot.root/build/glibc/ is empty. >>>>>> >>>>>> Only because you're not inside the container, where the mount exists. >>>>>> Containers are weird ;-) >>>>>> >>>>>>> error: test-container.c:235: can't mount /ssd/src/glibc onto >>>>>>> /build/glibc/testroot.root/ssd/src/glibc >>>>>> >>>>>> Sigh, you have "too many permissions" :-P Again, containers are weird. >>>>>> >>>>>> You may be able to run test-container manually, but test-container >>>>>> itself is built against the just-built glibc >>>>>> >>>>>>>> Also, selinux might be interfering. >>>>>>> >>>>>>> That doesn't sound encouraging. Anything I should look at/for? >>>>>> >>>>>> Dunno, I typically disable selinux. >>>>> >>>>> I haven't been able to make that work yet but I also haven't tried >>>>> too hard. I'll keep at it. >>>>> >>>>>> >>>>>> Just for paranoia's sake... does all this work on a newer Fedora? >>>>> >>>>> Yes. I just installed F33 on my laptop and it works fine there. >>>>> I haven't changed my main workstation though. It was a pain to >>>>> set up. >>>> >>>> I finally bit the bullet and upgraded my workstation to Fedora >>>> 35, partly in hopes of resolving the Glibc test suite problems. >>>> I now get the failures below with the top of GCC 12 and Glibc >>>> trunk, even after disabling SELinux by running setenforce 0, >>>> as well as after permanently disabling it in /etc/selinux/config. >>>> Is there something else I should try? >>>> >>>> Thanks >>>> Martin >>>> >>>> UNSUPPORTED: assert/tst-assert-c++ >>>> UNSUPPORTED: assert/tst-assert-g++ >>>> UNSUPPORTED: debug/tst-chk4 >>>> UNSUPPORTED: debug/tst-chk5 >>>> UNSUPPORTED: debug/tst-chk6 >>>> UNSUPPORTED: debug/tst-chk8 >>>> UNSUPPORTED: debug/tst-lfschk4 >>>> UNSUPPORTED: debug/tst-lfschk5 >>>> UNSUPPORTED: debug/tst-lfschk6 >>>> UNSUPPORTED: dlfcn/bug-atexit3 >>>> UNSUPPORTED: elf/tst-audit10 >>>> UNSUPPORTED: elf/tst-avx512 >>>> FAIL: elf/tst-dlopen-self-container >>>> FAIL: elf/tst-dlopen-tlsmodid-container >>>> UNSUPPORTED: elf/tst-env-setuid >>>> UNSUPPORTED: elf/tst-env-setuid-tunables >>>> FAIL: elf/tst-glibc-hwcaps-2-cache >>>> FAIL: elf/tst-glibc-hwcaps-cache >>>> FAIL: elf/tst-glibc-hwcaps-prepend-cache >>>> XPASS: elf/tst-ifunc-isa-1 >>>> XPASS: elf/tst-ifunc-isa-1-static >>>> XPASS: elf/tst-ifunc-isa-2 >>>> XPASS: elf/tst-ifunc-isa-2-static >>>> FAIL: elf/tst-ldconfig-bad-aux-cache >>>> FAIL: elf/tst-ldconfig-ld_so_conf-update >>>> FAIL: elf/tst-pldd >>>> FAIL: elf/tst-preload-pthread-libc >>>> XPASS: elf/tst-protected1a >>>> XPASS: elf/tst-protected1b >>>> FAIL: grp/tst-initgroups1 >>>> FAIL: grp/tst-initgroups2 >>>> FAIL: locale/tst-localedef-path-norm >>>> FAIL: localedata/tst-localedef-hardlinks >>>> UNSUPPORTED: math/test-double-libmvec-acos-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-acosh-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-asin-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-asinh-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-atan-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-atan2-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-atanh-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-cbrt-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-cos-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-cosh-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-erf-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-erfc-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-exp-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-exp10-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-exp2-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-expm1-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-hypot-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-log-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-log10-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-log1p-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-log2-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-pow-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-sin-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-sincos-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-sinh-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-tan-avx512f >>>> UNSUPPORTED: math/test-double-libmvec-tanh-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-acosf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-acoshf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-asinf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-asinhf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-atan2f-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-atanf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-atanhf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-cbrtf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-cosf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-coshf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-erfcf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-erff-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-exp10f-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-exp2f-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-expf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-expm1f-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-hypotf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-log10f-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-log1pf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-log2f-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-logf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-powf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-sincosf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-sinf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-sinhf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-tanf-avx512f >>>> UNSUPPORTED: math/test-float-libmvec-tanhf-avx512f >>>> UNSUPPORTED: misc/tst-adjtimex >>>> UNSUPPORTED: misc/tst-clock_adjtime >>>> UNSUPPORTED: misc/tst-ntp_adjtime >>>> UNSUPPORTED: misc/tst-pkey >>>> UNSUPPORTED: nptl/tst-cancel24 >>>> UNSUPPORTED: nptl/tst-cancel24-static >>>> UNSUPPORTED: nptl/tst-minstack-throw >>>> UNSUPPORTED: nptl/tst-once5 >>>> FAIL: nptl/tst-pthread-getattr >>>> UNSUPPORTED: nptl/tst-thread-exit-clobber >>>> UNSUPPORTED: nptl/tst-thread_local1 >>>> FAIL: nss/tst-nss-compat1 >>>> FAIL: nss/tst-nss-db-endgrent >>>> FAIL: nss/tst-nss-db-endpwent >>>> FAIL: nss/tst-nss-files-hosts-long >>>> FAIL: nss/tst-nss-test3 >>>> FAIL: nss/tst-reload1 >>>> FAIL: nss/tst-reload2 >>>> FAIL: posix/bug-ga2 >>>> UNSUPPORTED: posix/bug-ga2-mem >>>> FAIL: posix/tst-vfork3 >>>> UNSUPPORTED: posix/tst-vfork3-mem >>>> UNSUPPORTED: resolv/mtrace-tst-leaks2 >>>> FAIL: resolv/tst-leaks2 >>>> UNSUPPORTED: stdlib/tst-quick_exit >>>> UNSUPPORTED: stdlib/tst-secure-getenv >>>> FAIL: stdlib/tst-system >>>> UNSUPPORTED: stdlib/tst-thread-quick_exit >>>> UNSUPPORTED: string/tst-memchr-rtm >>>> UNSUPPORTED: string/tst-memcmp-rtm >>>> UNSUPPORTED: string/tst-memmove-rtm >>>> UNSUPPORTED: string/tst-memrchr-rtm >>>> UNSUPPORTED: string/tst-memset-rtm >>>> UNSUPPORTED: string/tst-strchr-rtm >>>> UNSUPPORTED: string/tst-strcpy-rtm >>>> FAIL: string/tst-strerror >>>> UNSUPPORTED: string/tst-strlen-rtm >>>> UNSUPPORTED: string/tst-strncmp-rtm >>>> UNSUPPORTED: string/tst-strrchr-rtm >>>> FAIL: string/tst-strsignal >>>> UNSUPPORTED: time/tst-clock_settime >>>> UNSUPPORTED: time/tst-settimeofday >>>> Summary of test results: >>>> 27 FAIL >>>> 4904 PASS >>>> 96 UNSUPPORTED >>>> 16 XFAIL >>>> 6 XPASS >>> >>> See: >>> >>> https://sourceware.org/bugzilla/show_bug.cgi?id=28455 >>> >>> My last patch is at >>> >>> https://patchwork.sourceware.org/project/glibc/patch/20220104140009.1578867-1-hjl.tools@gmail.com/ >> Thanks, but I still get the same results even with the patch >> applied and after rebuilding everything. The new test added >> by the patch, elf/tst-global2, passes. Am I missing something >> else or is this still some container problem? > > The filesystem I'm using is mounted with these flags: > > rw,nosuid,nodev,relatime,x-gvfs-show > > On a hunch I tried a different filesystem, one with these flags: > > rw,relatime > > That changes things, making me wonder if one of the bits (nosuid?) > might be interfering with the container magic? > > I still don't get a clean build on the other filesystem, but I see > no failures, only unsupported results (below). The exit status of > all those I checked is 77. Are these results expected? Yes, 77 is the internal exit magic number that states is was not a failure, but rather that the system lacks either proper tools or kernel/processor support. > > Martin > > UNSUPPORTED: assert/tst-assert-c++ > UNSUPPORTED: assert/tst-assert-g++ It means that the provided C++ compiler does not support thread_local or if CXX is not set. > UNSUPPORTED: debug/tst-fortify-cc-default-1 > UNSUPPORTED: debug/tst-fortify-cc-default-2 > UNSUPPORTED: debug/tst-fortify-cc-default-3 > UNSUPPORTED: debug/tst-fortify-cc-lfs-1 > UNSUPPORTED: debug/tst-fortify-cc-lfs-2 > UNSUPPORTED: debug/tst-fortify-cc-lfs-3 > UNSUPPORTED: debug/tst-fortify-cc-nongnu-1 > UNSUPPORTED: debug/tst-fortify-cc-nongnu-2 > UNSUPPORTED: debug/tst-fortify-cc-nongnu-3 These are disabled if CXX is not set to a proper C++ compiler. > UNSUPPORTED: dlfcn/bug-atexit3 Same. > UNSUPPORTED: elf/tst-audit10 > UNSUPPORTED: elf/tst-avx512 These requires a processor with support for AVX512. > UNSUPPORTED: elf/tst-env-setuid > UNSUPPORTED: elf/tst-env-setuid-tunables These fail if the file system is mounted nosuid. > XPASS: elf/tst-ifunc-isa-1 > XPASS: elf/tst-ifunc-isa-1-static > XPASS: elf/tst-ifunc-isa-2 > XPASS: elf/tst-ifunc-isa-2-static These are marked as xfail to now thrown an issue if LLD is used instead of binutils. I think maybe we mark as xfail iff lld is used. > XPASS: elf/tst-protected1a > XPASS: elf/tst-protected1b These are marked XFAIL because a gcc and binutils issue [1] [2]. I think with current minimum supported versions we can remove the xfail. > UNSUPPORTED: math/test-double-libmvec-acos-avx512f > UNSUPPORTED: math/test-double-libmvec-acosh-avx512f > UNSUPPORTED: math/test-double-libmvec-asin-avx512f > UNSUPPORTED: math/test-double-libmvec-asinh-avx512f > UNSUPPORTED: math/test-double-libmvec-atan-avx512f > UNSUPPORTED: math/test-double-libmvec-atan2-avx512f > UNSUPPORTED: math/test-double-libmvec-atanh-avx512f > UNSUPPORTED: math/test-double-libmvec-cbrt-avx512f > UNSUPPORTED: math/test-double-libmvec-cos-avx512f > UNSUPPORTED: math/test-double-libmvec-cosh-avx512f > UNSUPPORTED: math/test-double-libmvec-erf-avx512f > UNSUPPORTED: math/test-double-libmvec-erfc-avx512f > UNSUPPORTED: math/test-double-libmvec-exp-avx512f > UNSUPPORTED: math/test-double-libmvec-exp10-avx512f > UNSUPPORTED: math/test-double-libmvec-exp2-avx512f > UNSUPPORTED: math/test-double-libmvec-expm1-avx512f > UNSUPPORTED: math/test-double-libmvec-hypot-avx512f > UNSUPPORTED: math/test-double-libmvec-log-avx512f > UNSUPPORTED: math/test-double-libmvec-log10-avx512f > UNSUPPORTED: math/test-double-libmvec-log1p-avx512f > UNSUPPORTED: math/test-double-libmvec-log2-avx512f > UNSUPPORTED: math/test-double-libmvec-pow-avx512f > UNSUPPORTED: math/test-double-libmvec-sin-avx512f > UNSUPPORTED: math/test-double-libmvec-sincos-avx512f > UNSUPPORTED: math/test-double-libmvec-sinh-avx512f > UNSUPPORTED: math/test-double-libmvec-tan-avx512f > UNSUPPORTED: math/test-double-libmvec-tanh-avx512f > UNSUPPORTED: math/test-float-libmvec-acosf-avx512f > UNSUPPORTED: math/test-float-libmvec-acoshf-avx512f > UNSUPPORTED: math/test-float-libmvec-asinf-avx512f > UNSUPPORTED: math/test-float-libmvec-asinhf-avx512f > UNSUPPORTED: math/test-float-libmvec-atan2f-avx512f > UNSUPPORTED: math/test-float-libmvec-atanf-avx512f > UNSUPPORTED: math/test-float-libmvec-atanhf-avx512f > UNSUPPORTED: math/test-float-libmvec-cbrtf-avx512f > UNSUPPORTED: math/test-float-libmvec-cosf-avx512f > UNSUPPORTED: math/test-float-libmvec-coshf-avx512f > UNSUPPORTED: math/test-float-libmvec-erfcf-avx512f > UNSUPPORTED: math/test-float-libmvec-erff-avx512f > UNSUPPORTED: math/test-float-libmvec-exp10f-avx512f > UNSUPPORTED: math/test-float-libmvec-exp2f-avx512f > UNSUPPORTED: math/test-float-libmvec-expf-avx512f > UNSUPPORTED: math/test-float-libmvec-expm1f-avx512f > UNSUPPORTED: math/test-float-libmvec-hypotf-avx512f > UNSUPPORTED: math/test-float-libmvec-log10f-avx512f > UNSUPPORTED: math/test-float-libmvec-log1pf-avx512f > UNSUPPORTED: math/test-float-libmvec-log2f-avx512f > UNSUPPORTED: math/test-float-libmvec-logf-avx512f > UNSUPPORTED: math/test-float-libmvec-powf-avx512f > UNSUPPORTED: math/test-float-libmvec-sincosf-avx512f > UNSUPPORTED: math/test-float-libmvec-sinf-avx512f > UNSUPPORTED: math/test-float-libmvec-sinhf-avx512f > UNSUPPORTED: math/test-float-libmvec-tanf-avx512f > UNSUPPORTED: math/test-float-libmvec-tanhf-avx512f These all are require AVX512 as well. > UNSUPPORTED: misc/tst-adjtimex > UNSUPPORTED: misc/tst-clock_adjtime > UNSUPPORTED: misc/tst-ntp_adjtime There are ran only if GLIBC_TEST_ALLOW_TIME_SETTING env var is set (since they alter the system clock). > UNSUPPORTED: misc/tst-pkey It requires kernel support for pkey_alloc syscall. > UNSUPPORTED: nptl/tst-cancel24 > UNSUPPORTED: nptl/tst-cancel24-static > UNSUPPORTED: nptl/tst-minstack-throw > UNSUPPORTED: nptl/tst-once5 > UNSUPPORTED: nptl/tst-thread-exit-clobber > UNSUPPORTED: nptl/tst-thread_local1 > UNSUPPORTED: stdlib/tst-quick_exit > UNSUPPORTED: stdlib/tst-secure-getenv > UNSUPPORTED: stdlib/tst-thread-quick_exit These all require CXX to be properly set. > UNSUPPORTED: string/tst-memchr-rtm > UNSUPPORTED: string/tst-memcmp-rtm > UNSUPPORTED: string/tst-memmove-rtm > UNSUPPORTED: string/tst-memrchr-rtm > UNSUPPORTED: string/tst-memset-rtm > UNSUPPORTED: string/tst-strchr-rtm > UNSUPPORTED: string/tst-strcpy-rtm > UNSUPPORTED: string/tst-strlen-rtm > UNSUPPORTED: string/tst-strncmp-rtm > UNSUPPORTED: string/tst-strrchr-rtm These require a CPU with TSX enabled. > UNSUPPORTED: time/tst-clock_settime > UNSUPPORTED: time/tst-settimeofday Same as GLIBC_TEST_ALLOW_TIME_SETTING. > Summary of test results: > 4937 PASS > 95 UNSUPPORTED > 16 XFAIL > 6 XPASS [1] https://sourceware.org/bugzilla/show_bug.cgi?id=17709 [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65248 ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2022-01-17 18:04 ` Adhemerval Zanella @ 2022-01-17 19:09 ` Joseph Myers 2022-01-20 22:23 ` Martin Sebor 1 sibling, 0 replies; 23+ messages in thread From: Joseph Myers @ 2022-01-17 19:09 UTC (permalink / raw) To: Adhemerval Zanella; +Cc: Martin Sebor, H.J. Lu, GNU C Library On Mon, 17 Jan 2022, Adhemerval Zanella via Libc-alpha wrote: > > XPASS: elf/tst-protected1a > > XPASS: elf/tst-protected1b > > These are marked XFAIL because a gcc and binutils issue [1] [2]. > I think with current minimum supported versions we can remove > the xfail. I think this only works on a few architectures. -- Joseph S. Myers joseph@codesourcery.com ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux (due to test-container?) 2022-01-17 18:04 ` Adhemerval Zanella 2022-01-17 19:09 ` Joseph Myers @ 2022-01-20 22:23 ` Martin Sebor 1 sibling, 0 replies; 23+ messages in thread From: Martin Sebor @ 2022-01-20 22:23 UTC (permalink / raw) To: Adhemerval Zanella, H.J. Lu; +Cc: GNU C Library On 1/17/22 11:04, Adhemerval Zanella wrote: > > > On 14/01/2022 20:51, Martin Sebor via Libc-alpha wrote: >> On 1/12/22 16:24, Martin Sebor wrote: >>> On 1/12/22 15:13, H.J. Lu wrote: >>>> On Wed, Jan 12, 2022 at 2:05 PM Martin Sebor via Libc-alpha >>>> <libc-alpha@sourceware.org> wrote: >>>>> >>>>> On 5/13/21 15:29, Martin Sebor wrote: >>>>>> On 4/28/21 5:54 PM, DJ Delorie wrote: >>>>>>> Martin Sebor <msebor@gmail.com> writes: >>>>>>>>> (which should be bind-mounted inside your test chroot, which would be >>>>>>>>> /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3) >>>>>>>> >>>>>>>> /build/glibc/testroot.root/build/glibc/ is empty. >>>>>>> >>>>>>> Only because you're not inside the container, where the mount exists. >>>>>>> Containers are weird ;-) >>>>>>> >>>>>>>> error: test-container.c:235: can't mount /ssd/src/glibc onto >>>>>>>> /build/glibc/testroot.root/ssd/src/glibc >>>>>>> >>>>>>> Sigh, you have "too many permissions" :-P Again, containers are weird. >>>>>>> >>>>>>> You may be able to run test-container manually, but test-container >>>>>>> itself is built against the just-built glibc >>>>>>> >>>>>>>>> Also, selinux might be interfering. >>>>>>>> >>>>>>>> That doesn't sound encouraging. Anything I should look at/for? >>>>>>> >>>>>>> Dunno, I typically disable selinux. >>>>>> >>>>>> I haven't been able to make that work yet but I also haven't tried >>>>>> too hard. I'll keep at it. >>>>>> >>>>>>> >>>>>>> Just for paranoia's sake... does all this work on a newer Fedora? >>>>>> >>>>>> Yes. I just installed F33 on my laptop and it works fine there. >>>>>> I haven't changed my main workstation though. It was a pain to >>>>>> set up. >>>>> >>>>> I finally bit the bullet and upgraded my workstation to Fedora >>>>> 35, partly in hopes of resolving the Glibc test suite problems. >>>>> I now get the failures below with the top of GCC 12 and Glibc >>>>> trunk, even after disabling SELinux by running setenforce 0, >>>>> as well as after permanently disabling it in /etc/selinux/config. >>>>> Is there something else I should try? >>>>> >>>>> Thanks >>>>> Martin >>>>> >>>>> UNSUPPORTED: assert/tst-assert-c++ >>>>> UNSUPPORTED: assert/tst-assert-g++ >>>>> UNSUPPORTED: debug/tst-chk4 >>>>> UNSUPPORTED: debug/tst-chk5 >>>>> UNSUPPORTED: debug/tst-chk6 >>>>> UNSUPPORTED: debug/tst-chk8 >>>>> UNSUPPORTED: debug/tst-lfschk4 >>>>> UNSUPPORTED: debug/tst-lfschk5 >>>>> UNSUPPORTED: debug/tst-lfschk6 >>>>> UNSUPPORTED: dlfcn/bug-atexit3 >>>>> UNSUPPORTED: elf/tst-audit10 >>>>> UNSUPPORTED: elf/tst-avx512 >>>>> FAIL: elf/tst-dlopen-self-container >>>>> FAIL: elf/tst-dlopen-tlsmodid-container >>>>> UNSUPPORTED: elf/tst-env-setuid >>>>> UNSUPPORTED: elf/tst-env-setuid-tunables >>>>> FAIL: elf/tst-glibc-hwcaps-2-cache >>>>> FAIL: elf/tst-glibc-hwcaps-cache >>>>> FAIL: elf/tst-glibc-hwcaps-prepend-cache >>>>> XPASS: elf/tst-ifunc-isa-1 >>>>> XPASS: elf/tst-ifunc-isa-1-static >>>>> XPASS: elf/tst-ifunc-isa-2 >>>>> XPASS: elf/tst-ifunc-isa-2-static >>>>> FAIL: elf/tst-ldconfig-bad-aux-cache >>>>> FAIL: elf/tst-ldconfig-ld_so_conf-update >>>>> FAIL: elf/tst-pldd >>>>> FAIL: elf/tst-preload-pthread-libc >>>>> XPASS: elf/tst-protected1a >>>>> XPASS: elf/tst-protected1b >>>>> FAIL: grp/tst-initgroups1 >>>>> FAIL: grp/tst-initgroups2 >>>>> FAIL: locale/tst-localedef-path-norm >>>>> FAIL: localedata/tst-localedef-hardlinks >>>>> UNSUPPORTED: math/test-double-libmvec-acos-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-acosh-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-asin-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-asinh-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-atan-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-atan2-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-atanh-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-cbrt-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-cos-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-cosh-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-erf-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-erfc-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-exp-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-exp10-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-exp2-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-expm1-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-hypot-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-log-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-log10-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-log1p-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-log2-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-pow-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-sin-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-sincos-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-sinh-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-tan-avx512f >>>>> UNSUPPORTED: math/test-double-libmvec-tanh-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-acosf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-acoshf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-asinf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-asinhf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-atan2f-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-atanf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-atanhf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-cbrtf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-cosf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-coshf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-erfcf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-erff-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-exp10f-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-exp2f-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-expf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-expm1f-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-hypotf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-log10f-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-log1pf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-log2f-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-logf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-powf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-sincosf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-sinf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-sinhf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-tanf-avx512f >>>>> UNSUPPORTED: math/test-float-libmvec-tanhf-avx512f >>>>> UNSUPPORTED: misc/tst-adjtimex >>>>> UNSUPPORTED: misc/tst-clock_adjtime >>>>> UNSUPPORTED: misc/tst-ntp_adjtime >>>>> UNSUPPORTED: misc/tst-pkey >>>>> UNSUPPORTED: nptl/tst-cancel24 >>>>> UNSUPPORTED: nptl/tst-cancel24-static >>>>> UNSUPPORTED: nptl/tst-minstack-throw >>>>> UNSUPPORTED: nptl/tst-once5 >>>>> FAIL: nptl/tst-pthread-getattr >>>>> UNSUPPORTED: nptl/tst-thread-exit-clobber >>>>> UNSUPPORTED: nptl/tst-thread_local1 >>>>> FAIL: nss/tst-nss-compat1 >>>>> FAIL: nss/tst-nss-db-endgrent >>>>> FAIL: nss/tst-nss-db-endpwent >>>>> FAIL: nss/tst-nss-files-hosts-long >>>>> FAIL: nss/tst-nss-test3 >>>>> FAIL: nss/tst-reload1 >>>>> FAIL: nss/tst-reload2 >>>>> FAIL: posix/bug-ga2 >>>>> UNSUPPORTED: posix/bug-ga2-mem >>>>> FAIL: posix/tst-vfork3 >>>>> UNSUPPORTED: posix/tst-vfork3-mem >>>>> UNSUPPORTED: resolv/mtrace-tst-leaks2 >>>>> FAIL: resolv/tst-leaks2 >>>>> UNSUPPORTED: stdlib/tst-quick_exit >>>>> UNSUPPORTED: stdlib/tst-secure-getenv >>>>> FAIL: stdlib/tst-system >>>>> UNSUPPORTED: stdlib/tst-thread-quick_exit >>>>> UNSUPPORTED: string/tst-memchr-rtm >>>>> UNSUPPORTED: string/tst-memcmp-rtm >>>>> UNSUPPORTED: string/tst-memmove-rtm >>>>> UNSUPPORTED: string/tst-memrchr-rtm >>>>> UNSUPPORTED: string/tst-memset-rtm >>>>> UNSUPPORTED: string/tst-strchr-rtm >>>>> UNSUPPORTED: string/tst-strcpy-rtm >>>>> FAIL: string/tst-strerror >>>>> UNSUPPORTED: string/tst-strlen-rtm >>>>> UNSUPPORTED: string/tst-strncmp-rtm >>>>> UNSUPPORTED: string/tst-strrchr-rtm >>>>> FAIL: string/tst-strsignal >>>>> UNSUPPORTED: time/tst-clock_settime >>>>> UNSUPPORTED: time/tst-settimeofday >>>>> Summary of test results: >>>>> 27 FAIL >>>>> 4904 PASS >>>>> 96 UNSUPPORTED >>>>> 16 XFAIL >>>>> 6 XPASS >>>> >>>> See: >>>> >>>> https://sourceware.org/bugzilla/show_bug.cgi?id=28455 >>>> >>>> My last patch is at >>>> >>>> https://patchwork.sourceware.org/project/glibc/patch/20220104140009.1578867-1-hjl.tools@gmail.com/ >>> Thanks, but I still get the same results even with the patch >>> applied and after rebuilding everything. The new test added >>> by the patch, elf/tst-global2, passes. Am I missing something >>> else or is this still some container problem? >> >> The filesystem I'm using is mounted with these flags: >> >> rw,nosuid,nodev,relatime,x-gvfs-show >> >> On a hunch I tried a different filesystem, one with these flags: >> >> rw,relatime >> >> That changes things, making me wonder if one of the bits (nosuid?) >> might be interfering with the container magic? >> >> I still don't get a clean build on the other filesystem, but I see >> no failures, only unsupported results (below). The exit status of >> all those I checked is 77. Are these results expected? > > Yes, 77 is the internal exit magic number that states is was not > a failure, but rather that the system lacks either proper tools or > kernel/processor support. Thanks a lot for the detailed analysis! I figured out what 77 meant but not yet why. I'm not nearly as concerned about the unsupported results as I was about failures but it would be nice to get a cleaner bill of health. Do you mind a few follow up questions? > >> >> Martin >> >> UNSUPPORTED: assert/tst-assert-c++ >> UNSUPPORTED: assert/tst-assert-g++ > > It means that the provided C++ compiler does not support thread_local > or if CXX is not set. > >> UNSUPPORTED: debug/tst-fortify-cc-default-1 >> UNSUPPORTED: debug/tst-fortify-cc-default-2 >> UNSUPPORTED: debug/tst-fortify-cc-default-3 >> UNSUPPORTED: debug/tst-fortify-cc-lfs-1 >> UNSUPPORTED: debug/tst-fortify-cc-lfs-2 >> UNSUPPORTED: debug/tst-fortify-cc-lfs-3 >> UNSUPPORTED: debug/tst-fortify-cc-nongnu-1 >> UNSUPPORTED: debug/tst-fortify-cc-nongnu-2 >> UNSUPPORTED: debug/tst-fortify-cc-nongnu-3 > > These are disabled if CXX is not set to a proper C++ compiler. I set CXX to all the right options (all the C++ packages I've tried compile) but I probably need to also set LD_LIBRARY_PATH to the new libstdc++ for runtime testing. Let me give that a try. > >> UNSUPPORTED: dlfcn/bug-atexit3 > > Same. > >> UNSUPPORTED: elf/tst-audit10 >> UNSUPPORTED: elf/tst-avx512 > > These requires a processor with support for AVX512. I have an Intel Core i9-9900K CPU with the avx and avx2 bits set. Is the AVX 512 something newer/different? > >> UNSUPPORTED: elf/tst-env-setuid >> UNSUPPORTED: elf/tst-env-setuid-tunables > > These fail if the file system is mounted nosuid. Just to be clear, this result is for a build on filesystem with the nosuid bit clear: /dev/mapper/fedora_bigbox-home on /home type ext4 (rw,relatime) > >> XPASS: elf/tst-ifunc-isa-1 >> XPASS: elf/tst-ifunc-isa-1-static >> XPASS: elf/tst-ifunc-isa-2 >> XPASS: elf/tst-ifunc-isa-2-static > > These are marked as xfail to now thrown an issue if LLD is used > instead of binutils. I think maybe we mark as xfail iff lld is > used. > >> XPASS: elf/tst-protected1a >> XPASS: elf/tst-protected1b > > These are marked XFAIL because a gcc and binutils issue [1] [2]. > I think with current minimum supported versions we can remove > the xfail. Ack. > >> UNSUPPORTED: math/test-double-libmvec-acos-avx512f >> UNSUPPORTED: math/test-double-libmvec-acosh-avx512f >> UNSUPPORTED: math/test-double-libmvec-asin-avx512f >> UNSUPPORTED: math/test-double-libmvec-asinh-avx512f >> UNSUPPORTED: math/test-double-libmvec-atan-avx512f >> UNSUPPORTED: math/test-double-libmvec-atan2-avx512f >> UNSUPPORTED: math/test-double-libmvec-atanh-avx512f >> UNSUPPORTED: math/test-double-libmvec-cbrt-avx512f >> UNSUPPORTED: math/test-double-libmvec-cos-avx512f >> UNSUPPORTED: math/test-double-libmvec-cosh-avx512f >> UNSUPPORTED: math/test-double-libmvec-erf-avx512f >> UNSUPPORTED: math/test-double-libmvec-erfc-avx512f >> UNSUPPORTED: math/test-double-libmvec-exp-avx512f >> UNSUPPORTED: math/test-double-libmvec-exp10-avx512f >> UNSUPPORTED: math/test-double-libmvec-exp2-avx512f >> UNSUPPORTED: math/test-double-libmvec-expm1-avx512f >> UNSUPPORTED: math/test-double-libmvec-hypot-avx512f >> UNSUPPORTED: math/test-double-libmvec-log-avx512f >> UNSUPPORTED: math/test-double-libmvec-log10-avx512f >> UNSUPPORTED: math/test-double-libmvec-log1p-avx512f >> UNSUPPORTED: math/test-double-libmvec-log2-avx512f >> UNSUPPORTED: math/test-double-libmvec-pow-avx512f >> UNSUPPORTED: math/test-double-libmvec-sin-avx512f >> UNSUPPORTED: math/test-double-libmvec-sincos-avx512f >> UNSUPPORTED: math/test-double-libmvec-sinh-avx512f >> UNSUPPORTED: math/test-double-libmvec-tan-avx512f >> UNSUPPORTED: math/test-double-libmvec-tanh-avx512f >> UNSUPPORTED: math/test-float-libmvec-acosf-avx512f >> UNSUPPORTED: math/test-float-libmvec-acoshf-avx512f >> UNSUPPORTED: math/test-float-libmvec-asinf-avx512f >> UNSUPPORTED: math/test-float-libmvec-asinhf-avx512f >> UNSUPPORTED: math/test-float-libmvec-atan2f-avx512f >> UNSUPPORTED: math/test-float-libmvec-atanf-avx512f >> UNSUPPORTED: math/test-float-libmvec-atanhf-avx512f >> UNSUPPORTED: math/test-float-libmvec-cbrtf-avx512f >> UNSUPPORTED: math/test-float-libmvec-cosf-avx512f >> UNSUPPORTED: math/test-float-libmvec-coshf-avx512f >> UNSUPPORTED: math/test-float-libmvec-erfcf-avx512f >> UNSUPPORTED: math/test-float-libmvec-erff-avx512f >> UNSUPPORTED: math/test-float-libmvec-exp10f-avx512f >> UNSUPPORTED: math/test-float-libmvec-exp2f-avx512f >> UNSUPPORTED: math/test-float-libmvec-expf-avx512f >> UNSUPPORTED: math/test-float-libmvec-expm1f-avx512f >> UNSUPPORTED: math/test-float-libmvec-hypotf-avx512f >> UNSUPPORTED: math/test-float-libmvec-log10f-avx512f >> UNSUPPORTED: math/test-float-libmvec-log1pf-avx512f >> UNSUPPORTED: math/test-float-libmvec-log2f-avx512f >> UNSUPPORTED: math/test-float-libmvec-logf-avx512f >> UNSUPPORTED: math/test-float-libmvec-powf-avx512f >> UNSUPPORTED: math/test-float-libmvec-sincosf-avx512f >> UNSUPPORTED: math/test-float-libmvec-sinf-avx512f >> UNSUPPORTED: math/test-float-libmvec-sinhf-avx512f >> UNSUPPORTED: math/test-float-libmvec-tanf-avx512f >> UNSUPPORTED: math/test-float-libmvec-tanhf-avx512f > > These all are require AVX512 as well. > >> UNSUPPORTED: misc/tst-adjtimex >> UNSUPPORTED: misc/tst-clock_adjtime >> UNSUPPORTED: misc/tst-ntp_adjtime > > There are ran only if GLIBC_TEST_ALLOW_TIME_SETTING env var is set > (since they alter the system clock). I see. > >> UNSUPPORTED: misc/tst-pkey > > It requires kernel support for pkey_alloc syscall. I'm using Fedora 35 with linux 5.15.12-200.fc35.x86_64. The man page says the syscall was was added in 4.9 so it seems something must be interfering with it. Let me look into what that might be. > >> UNSUPPORTED: nptl/tst-cancel24 >> UNSUPPORTED: nptl/tst-cancel24-static >> UNSUPPORTED: nptl/tst-minstack-throw >> UNSUPPORTED: nptl/tst-once5 >> UNSUPPORTED: nptl/tst-thread-exit-clobber >> UNSUPPORTED: nptl/tst-thread_local1 >> UNSUPPORTED: stdlib/tst-quick_exit >> UNSUPPORTED: stdlib/tst-secure-getenv >> UNSUPPORTED: stdlib/tst-thread-quick_exit > > These all require CXX to be properly set. Ack. > >> UNSUPPORTED: string/tst-memchr-rtm >> UNSUPPORTED: string/tst-memcmp-rtm >> UNSUPPORTED: string/tst-memmove-rtm >> UNSUPPORTED: string/tst-memrchr-rtm >> UNSUPPORTED: string/tst-memset-rtm >> UNSUPPORTED: string/tst-strchr-rtm >> UNSUPPORTED: string/tst-strcpy-rtm >> UNSUPPORTED: string/tst-strlen-rtm >> UNSUPPORTED: string/tst-strncmp-rtm >> UNSUPPORTED: string/tst-strrchr-rtm > > These require a CPU with TSX enabled. Okay, I guess I'll just accept these. > >> UNSUPPORTED: time/tst-clock_settime >> UNSUPPORTED: time/tst-settimeofday > > Same as GLIBC_TEST_ALLOW_TIME_SETTING. Ack. Thanks again! Martin > >> Summary of test results: >> 4937 PASS >> 95 UNSUPPORTED >> 16 XFAIL >> 6 XPASS > > > [1] https://sourceware.org/bugzilla/show_bug.cgi?id=17709 > [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65248 ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux 2020-12-09 21:17 ` Martin Sebor 2020-12-09 21:44 ` H.J. Lu @ 2020-12-16 10:21 ` Florian Weimer 1 sibling, 0 replies; 23+ messages in thread From: Florian Weimer @ 2020-12-16 10:21 UTC (permalink / raw) To: Martin Sebor; +Cc: H.J. Lu, GNU C Library * Martin Sebor: > It's been a while since I built Glibc with the system compiler > so I must have misremembered the results. Here they are for > my Fedora 29 machine (with libstdc++-static installed and with > --prefix=/usr): > > gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC) Please try installing gcc-c++ and libstdc++-static. Does it help? Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: tests failing on x86_64-linux 2020-12-09 18:17 tests failing on x86_64-linux Martin Sebor 2020-12-09 18:28 ` H.J. Lu @ 2020-12-09 19:03 ` Florian Weimer 1 sibling, 0 replies; 23+ messages in thread From: Florian Weimer @ 2020-12-09 19:03 UTC (permalink / raw) To: Martin Sebor via Libc-alpha * Martin Sebor via Libc-alpha: > I've been seeing quite a few test failures in recent builds, more > than I used to in the past. Are those expected? I configure with > no options other than --prefix=/usr and after building without > installing (i.e., just make -j16) run make -j16 check. You have likely configured glibc without --prefix=/usr. As a result, the default search path does not include /usr/lib64, and required GCC components cannot be found. Maybe we should just default to that prefix (and the appropriate prefix for Hurd). It's a common trap. Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill ^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2022-01-20 22:23 UTC | newest] Thread overview: 23+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-12-09 18:17 tests failing on x86_64-linux Martin Sebor 2020-12-09 18:28 ` H.J. Lu 2020-12-09 21:17 ` Martin Sebor 2020-12-09 21:44 ` H.J. Lu 2020-12-09 22:31 ` H.J. Lu 2020-12-10 2:50 ` H.J. Lu 2020-12-15 0:55 ` Martin Sebor 2021-04-28 20:07 ` tests failing on x86_64-linux (due to test-container?) Martin Sebor 2021-04-28 20:37 ` DJ Delorie 2021-04-28 21:50 ` Martin Sebor 2021-04-28 23:08 ` DJ Delorie 2021-04-28 23:42 ` Martin Sebor 2021-04-28 23:54 ` DJ Delorie 2021-05-13 21:29 ` Martin Sebor 2022-01-12 22:04 ` Martin Sebor 2022-01-12 22:13 ` H.J. Lu 2022-01-12 23:24 ` Martin Sebor 2022-01-14 23:51 ` Martin Sebor 2022-01-17 18:04 ` Adhemerval Zanella 2022-01-17 19:09 ` Joseph Myers 2022-01-20 22:23 ` Martin Sebor 2020-12-16 10:21 ` tests failing on x86_64-linux Florian Weimer 2020-12-09 19:03 ` Florian Weimer
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).