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-02-16 19:32:04 build results
Date: Thu, 17 Feb 2022 00:35:47 +0000	[thread overview]
Message-ID: <164505814701.11030.18415461839328775193@build9-trusty-cs.sje.mentorg.com> (raw)

All regressions:

FAIL: compilers-arc-linux-gnu glibc arc-linux-gnu build
FAIL: compilers-arc-linux-gnuhf glibc arc-linux-gnuhf build
FAIL: compilers-arceb-linux-gnu glibc arceb-linux-gnu build
FAIL: compilers-sh4-linux-gnu glibc sh4-linux-gnu build
FAIL: compilers-sh4eb-linux-gnu glibc sh4eb-linux-gnu build

All failures:

FAIL: compilers-arc-linux-gnu glibc arc-linux-gnu build
FAIL: compilers-arc-linux-gnuhf glibc arc-linux-gnuhf build
FAIL: compilers-arceb-linux-gnu glibc arceb-linux-gnu build
FAIL: compilers-sh4-linux-gnu glibc sh4-linux-gnu build
FAIL: compilers-sh4eb-linux-gnu glibc sh4eb-linux-gnu build

Component versions for this build:

binutils: vcs-mainline (c212f39d9a82c6c09f4a1447d9d2ff09843827c5)
gcc: vcs-mainline (fe581e63431bb1115d8a4945ba457f05e33dc6bb)
glibc: vcs-mainline (790a607e234aa10d4b977a1b80aebe8a2acac970)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (294372afde326b8c277f738f3f8340cdd86f5b92)
hurd: vcs-mainline (d2ce4a404f6dc016e650c46a117c3ce278af7350)
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-17  0:35 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=164505814701.11030.18415461839328775193@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).