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-31 14:19:33 build results
Date: Wed, 31 Aug 2022 19:20:48 +0000	[thread overview]
Message-ID: <166197364832.8453.7235436248828371717@build9-trusty-cs.sje.mentorg.com> (raw)

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:

UNRESOLVED -> PASS: glibcs-i686-gnu build
UNRESOLVED -> PASS: glibcs-i686-gnu check
FAIL -> PASS: glibcs-i686-gnu check-compilers
UNRESOLVED -> PASS: glibcs-i686-gnu configure
UNRESOLVED -> PASS: glibcs-i686-gnu install
UNRESOLVED -> PASS: glibcs-i686-gnu mkdir
UNRESOLVED -> PASS: glibcs-i686-gnu mkdir-lib
UNRESOLVED -> PASS: glibcs-i686-gnu rm

Component versions for this build:

binutils: vcs-mainline (945e66a74d6dd3a94bd5f1ee5b132de42337eb4a)
gcc: vcs-mainline (b3048b6ffb126a4624f66bad713fe6d1dc6dc13d)
glibc: vcs-mainline (c7509d49c4e8fa494120c5ead21338559dad16f5)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (66775cd2279be8e81269c06575c836900aa64793)
hurd: vcs-mainline (298c7dadc6844163dccc8938756093f1e0a3ce05)
linux: 5.19 (5.19)
mig: vcs-mainline (68b3d8fe3a9595b7a5cb2bb6bc5973ba26139704)
mpc: 1.2.1 (1.2.1)
mpfr: 4.1.0 (4.1.0)

                 reply	other threads:[~2022-08-31 19:20 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=166197364832.8453.7235436248828371717@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).