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-04-16 08:32:43 build results
Date: Sat, 16 Apr 2022 13:21:34 +0000	[thread overview]
Message-ID: <165011529448.3213.1771117598035932943@build9-trusty-cs.sje.mentorg.com> (raw)

New regressions:

FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch build
FAIL: glibcs-x86_64-linux-gnu-minimal build

All regressions:

FAIL: glibcs-aarch64-linux-gnu check-compilers
FAIL: glibcs-aarch64-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-sh4-linux-gnu check-compilers
FAIL: glibcs-sh4eb-linux-gnu check-compilers
FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch build
FAIL: glibcs-x86_64-linux-gnu-minimal build

All failures:

FAIL: glibcs-aarch64-linux-gnu check-compilers
FAIL: glibcs-aarch64-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-sh4-linux-gnu check-compilers
FAIL: glibcs-sh4eb-linux-gnu check-compilers
FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch build
FAIL: glibcs-x86_64-linux-gnu-minimal build

All changed results:

PASS -> FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch build
PASS -> UNRESOLVED: glibcs-x86_64-linux-gnu-disable-multi-arch check
PASS -> UNRESOLVED: glibcs-x86_64-linux-gnu-disable-multi-arch install
PASS -> UNRESOLVED: glibcs-x86_64-linux-gnu-disable-multi-arch mkdir-lib
PASS -> FAIL: glibcs-x86_64-linux-gnu-minimal build
PASS -> UNRESOLVED: glibcs-x86_64-linux-gnu-minimal check
PASS -> UNRESOLVED: glibcs-x86_64-linux-gnu-minimal install
PASS -> UNRESOLVED: glibcs-x86_64-linux-gnu-minimal mkdir-lib

Component versions for this build:

binutils: vcs-mainline (3beda815bdd784aa51255fab86dd505dae460bd1)
gcc: vcs-mainline (587953f0931d6af870c8f8fdba64985a27836914)
glibc: vcs-mainline (23102686ec67b856a2d4fd25ddaa1c0b8d175c4f)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (cf882205ff73cf155a9c9f48d6b41d7ad5f71f9b)
hurd: vcs-mainline (88ee4ae44bd64e869bca79d0a6c6e6d4577b7170)
linux: 5.17 (5.17)
mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f)
mpc: 1.2.1 (1.2.1)
mpfr: 4.1.0 (4.1.0)


                 reply	other threads:[~2022-04-16 13:21 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=165011529448.3213.1771117598035932943@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).