public inbox for libc-testresults@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <josmyers@redhat.com>
To: libc-testresults@sourceware.org
Subject: GCC mainline glibcs 2024-05-25 20:04:11 build results
Date: Sun, 26 May 2024 00:09:53 +0000	[thread overview]
Message-ID: <171668219366.3969018.2083408344085746052@tor.usersys.redhat.com> (raw)

All regressions:

FAIL: glibcs-hppa-linux-gnu check-compilers
FAIL: glibcs-i486-linux-gnu check
FAIL: glibcs-i586-linux-gnu check
FAIL: glibcs-i686-gnu check
FAIL: glibcs-i686-linux-gnu check
FAIL: glibcs-i686-linux-gnu-disable-multi-arch check
FAIL: glibcs-i686-linux-gnu-no-pie check
FAIL: glibcs-x86_64-gnu check
FAIL: glibcs-x86_64-linux-gnu check
FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check
FAIL: glibcs-x86_64-linux-gnu-enable-fortify-source check
FAIL: glibcs-x86_64-linux-gnu-minimal check
FAIL: glibcs-x86_64-linux-gnu-no-pie check
FAIL: glibcs-x86_64-linux-gnu-x32 check
FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check

All failures:

FAIL: glibcs-hppa-linux-gnu check-compilers
FAIL: glibcs-i486-linux-gnu check
FAIL: glibcs-i586-linux-gnu check
FAIL: glibcs-i686-gnu check
FAIL: glibcs-i686-linux-gnu check
FAIL: glibcs-i686-linux-gnu-disable-multi-arch check
FAIL: glibcs-i686-linux-gnu-no-pie check
FAIL: glibcs-x86_64-gnu check
FAIL: glibcs-x86_64-linux-gnu check
FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check
FAIL: glibcs-x86_64-linux-gnu-enable-fortify-source check
FAIL: glibcs-x86_64-linux-gnu-minimal check
FAIL: glibcs-x86_64-linux-gnu-no-pie check
FAIL: glibcs-x86_64-linux-gnu-x32 check
FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check

Component versions for this build:

binutils: vcs-mainline (0daa17bf187cebd5b200f4fd5405cc55e75c391f)
gcc: vcs-mainline (28b508233a12c13295f960a2cb8a4864879acfb4)
glibc: vcs-mainline (caed1f5c0b2e31b5f4e0f21fea4b2c9ecd3b5b30)
gmp: 6.3.0 (6.3.0)
gnumach: vcs-mainline (0396920c68ce7c09b1aea5c24f25e8006114502f)
hurd: vcs-mainline (529d72a57521ff077dcca45e573b7592059b1061)
linux: 6.9 (6.9)
mig: vcs-mainline (d9d2d5936e71e65e8f35ca79cae3f07c00db3515)
mpc: 1.3.1 (1.3.1)
mpfr: 4.2.1 (4.2.1)


                 reply	other threads:[~2024-05-26  0:09 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=171668219366.3969018.2083408344085746052@tor.usersys.redhat.com \
    --to=josmyers@redhat.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).