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-02-07 02:38:10 build results
Date: Mon, 7 Feb 2022 07:22:30 +0000	[thread overview]
Message-ID: <164421855035.3742.2190173086793211815@build9-trusty-cs.sje.mentorg.com> (raw)

All regressions:

FAIL: glibcs-arc-linux-gnu check-compilers
FAIL: glibcs-arc-linux-gnuhf check-compilers
FAIL: glibcs-arceb-linux-gnu check-compilers
FAIL: glibcs-hppa-linux-gnu check
FAIL: glibcs-microblaze-linux-gnu check
FAIL: glibcs-microblazeel-linux-gnu check
FAIL: glibcs-or1k-linux-gnu-soft check-compilers
FAIL: glibcs-s390x-linux-gnu-O3 check
FAIL: glibcs-sh4-linux-gnu check-compilers
FAIL: glibcs-sh4eb-linux-gnu check-compilers
FAIL: glibcs-sparcv8-linux-gnu-leon3 check
FAIL: glibcs-sparcv9-linux-gnu check
FAIL: glibcs-sparcv9-linux-gnu-disable-multi-arch check

All failures:

FAIL: glibcs-arc-linux-gnu check-compilers
FAIL: glibcs-arc-linux-gnuhf check-compilers
FAIL: glibcs-arceb-linux-gnu check-compilers
FAIL: glibcs-hppa-linux-gnu check
FAIL: glibcs-microblaze-linux-gnu check
FAIL: glibcs-microblazeel-linux-gnu check
FAIL: glibcs-or1k-linux-gnu-soft check-compilers
FAIL: glibcs-s390x-linux-gnu-O3 check
FAIL: glibcs-sh4-linux-gnu check-compilers
FAIL: glibcs-sh4eb-linux-gnu check-compilers
FAIL: glibcs-sparcv8-linux-gnu-leon3 check
FAIL: glibcs-sparcv9-linux-gnu check
FAIL: glibcs-sparcv9-linux-gnu-disable-multi-arch check

Component versions for this build:

binutils: vcs-mainline (1a1bfce78f58cc934bf6ace4d03ddc87c9cbb860)
gcc: vcs-mainline (8eb329e963593342855b6072e5692659107337b7)
glibc: vcs-mainline (fa7ad1df1915c8a62f50e3a5b7e10f9c7118cd7f)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (afa3aaefb317f9b7b5691cb15f97998389d8ed43)
hurd: vcs-mainline (06c6a81aa2b8a7eb6c192d172840dea90345f557)
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-02-07  7:22 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=164421855035.3742.2190173086793211815@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: 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).