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-24 06:47:36 build results
Date: Mon, 24 Jan 2022 09:42:37 +0000 [thread overview]
Message-ID: <164301735771.12394.16100322475398699483@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
FAIL: glibcs-x86_64-linux-gnu check
FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check
FAIL: glibcs-x86_64-linux-gnu-minimal check
FAIL: glibcs-x86_64-linux-gnu-no-pie check
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
FAIL: glibcs-x86_64-linux-gnu check
FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check
FAIL: glibcs-x86_64-linux-gnu-minimal check
FAIL: glibcs-x86_64-linux-gnu-no-pie check
All changed results:
FAIL -> PASS: glibcs-i686-gnu check
Component versions for this build:
binutils: vcs-2.37 (cf0ac00a8451073d933a4f731837305ce8496bb8)
gcc: vcs-11 (806d0ce8cb0c1b690e6b5774a5eb3a1404a21253)
glibc: vcs-mainline (976db046bc3a3738f69255ae00b0a09b8e77fd9c)
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-24 9:42 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=164301735771.12394.16100322475398699483@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: link
Be 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).