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 2023-01-17 22:07:47 build results
Date: Wed, 18 Jan 2023 00:03:33 +0000	[thread overview]
Message-ID: <167400021345.1312665.8740594317178126600@build4-jammy-cs.sje.mentorg.com> (raw)

All regressions:

FAIL: glibcs-aarch64-linux-gnu check-compilers
FAIL: glibcs-aarch64-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-csky-linux-gnuabiv2 check-compilers
FAIL: glibcs-i486-linux-gnu check-compilers
FAIL: glibcs-i586-linux-gnu check-compilers
FAIL: glibcs-i686-linux-gnu check-compilers
FAIL: glibcs-i686-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-i686-linux-gnu-no-pie check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers
FAIL: glibcs-x86_64-linux-gnu check-compilers
FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-x86_64-linux-gnu-minimal check-compilers
FAIL: glibcs-x86_64-linux-gnu-no-pie check-compilers
FAIL: glibcs-x86_64-linux-gnu-x32 check-compilers
FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check-compilers

All failures:

FAIL: glibcs-aarch64-linux-gnu check-compilers
FAIL: glibcs-aarch64-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-csky-linux-gnuabiv2 check-compilers
FAIL: glibcs-i486-linux-gnu check-compilers
FAIL: glibcs-i586-linux-gnu check-compilers
FAIL: glibcs-i686-linux-gnu check-compilers
FAIL: glibcs-i686-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-i686-linux-gnu-no-pie check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers
FAIL: glibcs-x86_64-linux-gnu check-compilers
FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check-compilers
FAIL: glibcs-x86_64-linux-gnu-minimal check-compilers
FAIL: glibcs-x86_64-linux-gnu-no-pie check-compilers
FAIL: glibcs-x86_64-linux-gnu-x32 check-compilers
FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check-compilers

Component versions for this build:

binutils: vcs-mainline (ef497b741139492a40bee9132d29cb861926ca9c)
gcc: vcs-mainline (a75760374ee54768e5fd6a27080698bfbbd041ab)
glibc: vcs-mainline (55599d480437dcf129b41b95be32b48f2a9e5da9)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (454868c3d2d978808b845352ea1483d0cea50190)
hurd: vcs-mainline (cb8ac8c47b03833fa7eebcb2ce94801f13da2bd7)
linux: 6.1 (6.1)
mig: vcs-mainline (a9db7bcc04530e19223b5037bb8420fa4344b183)
mpc: 1.2.1 (1.2.1)
mpfr: 4.1.0 (4.1.0)

                 reply	other threads:[~2023-01-18  0:03 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=167400021345.1312665.8740594317178126600@build4-jammy-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).