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 11 glibcs 2022-01-19 08:54:26 build results Date: Wed, 19 Jan 2022 11:44:38 +0000 [thread overview] Message-ID: <164259267804.28490.1424401658030499205@build8-trusty-cs.sje.mentorg.com> (raw) All regressions: FAIL: glibcs-mips-linux-gnu check-compilers FAIL: glibcs-mips-linux-gnu-nan2008 check-compilers FAIL: glibcs-mips-linux-gnu-nan2008-soft check-compilers FAIL: glibcs-mips-linux-gnu-soft check-compilers FAIL: glibcs-mips64-linux-gnu-n32 check-compilers FAIL: glibcs-mips64-linux-gnu-n32-nan2008 check-compilers FAIL: glibcs-mips64-linux-gnu-n32-nan2008-soft check-compilers FAIL: glibcs-mips64-linux-gnu-n32-soft check-compilers FAIL: glibcs-mips64-linux-gnu-n64 check-compilers FAIL: glibcs-mips64-linux-gnu-n64-nan2008 check-compilers FAIL: glibcs-mips64-linux-gnu-n64-nan2008-soft check-compilers FAIL: glibcs-mips64-linux-gnu-n64-soft check-compilers FAIL: glibcs-mips64el-linux-gnu-n32 check-compilers FAIL: glibcs-mips64el-linux-gnu-n32-nan2008 check-compilers FAIL: glibcs-mips64el-linux-gnu-n32-nan2008-soft check-compilers FAIL: glibcs-mips64el-linux-gnu-n32-soft check-compilers FAIL: glibcs-mips64el-linux-gnu-n64 check-compilers FAIL: glibcs-mips64el-linux-gnu-n64-nan2008 check-compilers FAIL: glibcs-mips64el-linux-gnu-n64-nan2008-soft check-compilers FAIL: glibcs-mips64el-linux-gnu-n64-soft check-compilers FAIL: glibcs-mipsel-linux-gnu check-compilers FAIL: glibcs-mipsel-linux-gnu-nan2008 check-compilers FAIL: glibcs-mipsel-linux-gnu-nan2008-soft check-compilers FAIL: glibcs-mipsel-linux-gnu-soft check-compilers FAIL: glibcs-mipsisa32r6el-linux-gnu check-compilers FAIL: glibcs-mipsisa64r6el-linux-gnu-n32 check-compilers FAIL: glibcs-mipsisa64r6el-linux-gnu-n64 check-compilers All failures: FAIL: glibcs-mips-linux-gnu check-compilers FAIL: glibcs-mips-linux-gnu-nan2008 check-compilers FAIL: glibcs-mips-linux-gnu-nan2008-soft check-compilers FAIL: glibcs-mips-linux-gnu-soft check-compilers FAIL: glibcs-mips64-linux-gnu-n32 check-compilers FAIL: glibcs-mips64-linux-gnu-n32-nan2008 check-compilers FAIL: glibcs-mips64-linux-gnu-n32-nan2008-soft check-compilers FAIL: glibcs-mips64-linux-gnu-n32-soft check-compilers FAIL: glibcs-mips64-linux-gnu-n64 check-compilers FAIL: glibcs-mips64-linux-gnu-n64-nan2008 check-compilers FAIL: glibcs-mips64-linux-gnu-n64-nan2008-soft check-compilers FAIL: glibcs-mips64-linux-gnu-n64-soft check-compilers FAIL: glibcs-mips64el-linux-gnu-n32 check-compilers FAIL: glibcs-mips64el-linux-gnu-n32-nan2008 check-compilers FAIL: glibcs-mips64el-linux-gnu-n32-nan2008-soft check-compilers FAIL: glibcs-mips64el-linux-gnu-n32-soft check-compilers FAIL: glibcs-mips64el-linux-gnu-n64 check-compilers FAIL: glibcs-mips64el-linux-gnu-n64-nan2008 check-compilers FAIL: glibcs-mips64el-linux-gnu-n64-nan2008-soft check-compilers FAIL: glibcs-mips64el-linux-gnu-n64-soft check-compilers FAIL: glibcs-mipsel-linux-gnu check-compilers FAIL: glibcs-mipsel-linux-gnu-nan2008 check-compilers FAIL: glibcs-mipsel-linux-gnu-nan2008-soft check-compilers FAIL: glibcs-mipsel-linux-gnu-soft check-compilers FAIL: glibcs-mipsisa32r6el-linux-gnu check-compilers FAIL: glibcs-mipsisa64r6el-linux-gnu-n32 check-compilers FAIL: glibcs-mipsisa64r6el-linux-gnu-n64 check-compilers Component versions for this build: binutils: vcs-2.37 (cf0ac00a8451073d933a4f731837305ce8496bb8) gcc: vcs-11 (806d0ce8cb0c1b690e6b5774a5eb3a1404a21253) glibc: vcs-mainline (1e000d3d33211d5a954300e2a69b90f93f18a1a1) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (17b780b4be553833d41881a8fbe499d0c9cfbc7e) hurd: vcs-mainline (0ba67e20da488e1b715b5c33e3d08daeec3b8aba) linux: 5.16 (5.16) mig: vcs-mainline (cf4bcc3f1435eafa3ed8b5fadfa9698033d1e2df) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-01-19 11:44 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=164259267804.28490.1424401658030499205@build8-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).