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 compilers 2022-06-06 21:03:59 build results Date: Tue, 7 Jun 2022 01:26:56 +0000 [thread overview] Message-ID: <165456521610.6719.10492561684706526988@build9-trusty-cs.sje.mentorg.com> (raw) All regressions: FAIL: compilers-mips64-linux-gnu glibc mips64-linux-gnu-n32 build FAIL: compilers-mips64-linux-gnu-nan2008 glibc mips64-linux-gnu-n32-nan2008 build FAIL: compilers-mips64-linux-gnu-nan2008-soft glibc mips64-linux-gnu-n32-nan2008-soft build FAIL: compilers-mips64-linux-gnu-soft glibc mips64-linux-gnu-n32-soft build FAIL: compilers-mips64el-linux-gnu glibc mips64el-linux-gnu-n32 build FAIL: compilers-mips64el-linux-gnu-nan2008 glibc mips64el-linux-gnu-n32-nan2008 build FAIL: compilers-mips64el-linux-gnu-nan2008-soft glibc mips64el-linux-gnu-n32-nan2008-soft build FAIL: compilers-mips64el-linux-gnu-soft glibc mips64el-linux-gnu-n32-soft build All failures: FAIL: compilers-mips64-linux-gnu glibc mips64-linux-gnu-n32 build FAIL: compilers-mips64-linux-gnu-nan2008 glibc mips64-linux-gnu-n32-nan2008 build FAIL: compilers-mips64-linux-gnu-nan2008-soft glibc mips64-linux-gnu-n32-nan2008-soft build FAIL: compilers-mips64-linux-gnu-soft glibc mips64-linux-gnu-n32-soft build FAIL: compilers-mips64el-linux-gnu glibc mips64el-linux-gnu-n32 build FAIL: compilers-mips64el-linux-gnu-nan2008 glibc mips64el-linux-gnu-n32-nan2008 build FAIL: compilers-mips64el-linux-gnu-nan2008-soft glibc mips64el-linux-gnu-n32-nan2008-soft build FAIL: compilers-mips64el-linux-gnu-soft glibc mips64el-linux-gnu-n32-soft build Component versions for this build: binutils: vcs-mainline (691ade38bc45f4d4c89c0d6a3412bc160cf40a70) gcc: vcs-mainline (733a792a2b2e1662e738fa358b45a2720a8618a7) glibc: vcs-mainline (8521001731d6539382fa875f1cac9864c466ef27) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (151dfe9971ac2bd4d9afb440f2a5b2a4f9a58969) hurd: vcs-mainline (88ee4ae44bd64e869bca79d0a6c6e6d4577b7170) linux: 5.18 (5.18) mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-06-07 1:26 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=165456521610.6719.10492561684706526988@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).