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 2022-03-21 05:06:08 build results Date: Mon, 21 Mar 2022 09:29:30 +0000 [thread overview] Message-ID: <164785497034.1456.8460570397078823730@build9-trusty-cs.sje.mentorg.com> (raw) All regressions: FAIL: glibcs-aarch64-linux-gnu check-compilers FAIL: glibcs-aarch64-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-i486-linux-gnu check-compilers FAIL: glibcs-i586-linux-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-no-pie check-compilers FAIL: glibcs-sh4-linux-gnu check-compilers FAIL: glibcs-sh4eb-linux-gnu check-compilers 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-no-pie check-compilers FAIL: glibcs-x86_64-linux-gnu-x32 check-compilers FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check-compilers All failures: FAIL: glibcs-aarch64-linux-gnu check-compilers FAIL: glibcs-aarch64-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-i486-linux-gnu check-compilers FAIL: glibcs-i586-linux-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-no-pie check-compilers FAIL: glibcs-sh4-linux-gnu check-compilers FAIL: glibcs-sh4eb-linux-gnu check-compilers 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-no-pie check-compilers FAIL: glibcs-x86_64-linux-gnu-x32 check-compilers FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check-compilers Component versions for this build: binutils: vcs-mainline (062cda5a37967a4a2ab4f8b04032a6688018ee6b) gcc: vcs-mainline (6f30c4cd38b8385d62358065d795df590e752d6e) glibc: vcs-mainline (59c30d5708e4bfc1510176222f7772fe800ff9d2) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (f64bcd88f5cc9e44573c202daf3c0dcec199636b) hurd: vcs-mainline (866371cd8b06f20989eff1c58dff71535b3a0fa7) linux: 5.16 (5.16) mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-03-21 9:29 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=164785497034.1456.8460570397078823730@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).