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-01-06 05:41:16 build results
Date: Thu, 6 Jan 2022 10:36:38 +0000	[thread overview]
Message-ID: <164146539839.18017.14249937463763401946@build9-trusty-cs.sje.mentorg.com> (raw)

All regressions:

FAIL: glibcs-sh4-linux-gnu check-compilers
FAIL: glibcs-sh4eb-linux-gnu check-compilers

All failures:

FAIL: glibcs-sh4-linux-gnu check-compilers
FAIL: glibcs-sh4eb-linux-gnu check-compilers

All changed results:

(New test) -> PASS: glibcs-or1k-linux-gnu-soft build
(New test) -> PASS: glibcs-or1k-linux-gnu-soft check
(New test) -> PASS: glibcs-or1k-linux-gnu-soft check-compilers
(New test) -> PASS: glibcs-or1k-linux-gnu-soft cleanup
(New test) -> PASS: glibcs-or1k-linux-gnu-soft configure
(New test) -> PASS: glibcs-or1k-linux-gnu-soft install
(New test) -> PASS: glibcs-or1k-linux-gnu-soft mkdir
(New test) -> PASS: glibcs-or1k-linux-gnu-soft mkdir-lib
(New test) -> PASS: glibcs-or1k-linux-gnu-soft rm
(New test) -> PASS: glibcs-or1k-linux-gnu-soft save-logs

Component versions for this build:

binutils: vcs-mainline (f9f424229637e6a55a1fad3ae4b75e3900282098)
gcc: vcs-mainline (0fbefa25b3f928d97fb7fd61f1448a55e5ec612d)
glibc: vcs-mainline (c1fc366ec9e78e17ad3e2ecdb4c4cc662decc32b)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (63ed32b135317b7884c3feaa5b5e873aa15b7f07)
hurd: vcs-mainline (ad63bae03cf0eb9edced3803cbcd0cee02377050)
linux: 5.15 (5.15)
mig: vcs-mainline (e9482b80272f673f625ac80d49ffea6b79fb6117)
mpc: 1.2.1 (1.2.1)
mpfr: 4.1.0 (4.1.0)


                 reply	other threads:[~2022-01-06 10:36 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=164146539839.18017.14249937463763401946@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).