public inbox for libc-testresults@sourceware.org help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com> To: <libc-testresults@sourceware.org> Subject: GCC mainline glibcs 2021-10-13 10:58:13 build results Date: Wed, 13 Oct 2021 15:11:53 +0000 [thread overview] Message-ID: <163413791332.29003.9497786382729146066@build9-trusty-cs.sje.mentorg.com> (raw) All regressions: FAIL: glibcs-i486-linux-gnu check-compilers FAIL: glibcs-i586-linux-gnu check-compilers FAIL: glibcs-i686-gnu check-compilers FAIL: glibcs-i686-linux-gnu check-compilers FAIL: glibcs-i686-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-i686-linux-gnu-static-pie check-compilers FAIL: glibcs-s390x-linux-gnu-O3 build FAIL: glibcs-x86_64-linux-gnu check-compilers FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-x86_64-linux-gnu-static-pie check-compilers FAIL: glibcs-x86_64-linux-gnu-x32 check-compilers FAIL: glibcs-x86_64-linux-gnu-x32-static-pie check-compilers All failures: FAIL: glibcs-i486-linux-gnu check-compilers FAIL: glibcs-i586-linux-gnu check-compilers FAIL: glibcs-i686-gnu check-compilers FAIL: glibcs-i686-linux-gnu check-compilers FAIL: glibcs-i686-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-i686-linux-gnu-static-pie check-compilers FAIL: glibcs-s390x-linux-gnu-O3 build FAIL: glibcs-x86_64-linux-gnu check-compilers FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-x86_64-linux-gnu-minimal check-compilers FAIL: glibcs-x86_64-linux-gnu-static-pie check-compilers FAIL: glibcs-x86_64-linux-gnu-x32 check-compilers FAIL: glibcs-x86_64-linux-gnu-x32-static-pie check-compilers All changed results: FAIL -> PASS: glibcs-nios2-linux-gnu check Component versions for this build: binutils: vcs-mainline (777b054cf93ad2525b891ea15bbf8d5cd6a56339) gcc: vcs-mainline (a124c1b0a2595f285c0d8ed863b37b83e14a6566) glibc: vcs-mainline (e59ced238482fd71f3e493717f14f6507346741e) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (c96f937b78efc3130700724c60439f4f5cc2ef2f) hurd: vcs-mainline (5eac2a9ffd7629fcba1c4800c63f90f8ea32ad17) linux: 5.14 (5.14) mig: vcs-mainline (e9482b80272f673f625ac80d49ffea6b79fb6117) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2021-10-13 15:12 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=163413791332.29003.9497786382729146066@build9-trusty-cs.sje.mentorg.com \ --to=joseph@codesourcery.com \ --cc=libc-testresults@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).