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-01 06:31:44 build results
Date: Tue, 1 Feb 2022 11:30:43 +0000	[thread overview]
Message-ID: <164371504394.6673.10225132102802518892@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-or1k-linux-gnu-soft glibc or1k-linux-gnu-soft 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-or1k-linux-gnu-soft glibc or1k-linux-gnu-soft 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 (e327c35ef5768789d3ba41a629f178f5eec32790)
gcc: vcs-mainline (1bb52662574f6c98de48a5db8c180786e4a53039)
glibc: vcs-mainline (3fb18fd80c5900cc82748f3320b30516c57d24da)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (fb3cc15b1662f00c11d889584f6bc8e3a853c947)
hurd: vcs-mainline (f94e6284aa777ab7b63374759b35e0d8219e3d4d)
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-01 11:30 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=164371504394.6673.10225132102802518892@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).