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-08-27 17:40:07 build results
Date: Sat, 27 Aug 2022 22:41:51 +0000 [thread overview]
Message-ID: <166164011167.7093.546228344421704386@build9-trusty-cs.sje.mentorg.com> (raw)
New regressions:
FAIL: glibcs-powerpc64-linux-gnu check-compilers
FAIL: glibcs-powerpc64le-linux-gnu check-compilers
FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers
All regressions:
FAIL: glibcs-i686-linux-gnu-no-pie check
FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers
FAIL: glibcs-powerpc64-linux-gnu check-compilers
FAIL: glibcs-powerpc64le-linux-gnu check-compilers
FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-x86_64-linux-gnu-no-pie check
FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check
All failures:
FAIL: glibcs-i686-linux-gnu-no-pie check
FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers
FAIL: glibcs-powerpc64-linux-gnu check-compilers
FAIL: glibcs-powerpc64le-linux-gnu check-compilers
FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-x86_64-linux-gnu-no-pie check
FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check
All changed results:
PASS -> UNRESOLVED: glibcs-powerpc64-linux-gnu build
PASS -> UNRESOLVED: glibcs-powerpc64-linux-gnu check
PASS -> FAIL: glibcs-powerpc64-linux-gnu check-compilers
PASS -> UNRESOLVED: glibcs-powerpc64-linux-gnu configure
PASS -> UNRESOLVED: glibcs-powerpc64-linux-gnu install
PASS -> UNRESOLVED: glibcs-powerpc64-linux-gnu mkdir
PASS -> UNRESOLVED: glibcs-powerpc64-linux-gnu mkdir-lib
PASS -> UNRESOLVED: glibcs-powerpc64-linux-gnu rm
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu build
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu check
PASS -> FAIL: glibcs-powerpc64le-linux-gnu check-compilers
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu configure
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu install
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu mkdir
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu mkdir-lib
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu rm
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch build
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch check
PASS -> FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch configure
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch install
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch mkdir
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch mkdir-lib
PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch rm
Component versions for this build:
binutils: vcs-mainline (9c17922bfec7b9a0f6183b996cba5a9699f0da1a)
gcc: vcs-mainline (4d291ca6a48eeeef3f51b8ab8452fe2166f021ee)
glibc: vcs-mainline (d0e357ff45a75553dee3b17ed7d303bfa544f6fe)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (f2626beb39dc416ceebfa35076d89cd291e2b903)
hurd: vcs-mainline (772e292c2d47e9d93455e3c87ae0209a58a3da67)
linux: 5.19 (5.19)
mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f)
mpc: 1.2.1 (1.2.1)
mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-08-27 22:41 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=166164011167.7093.546228344421704386@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).