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-12-09 04:05:40 build results
Date: Sat, 9 Dec 2023 07:05:44 +0000	[thread overview]
Message-ID: <170210554437.762733.12111047953858468607@build4-jammy-cs.sje.mentorg.com> (raw)

All regressions:

FAIL: glibcs-hppa-linux-gnu check-compilers
FAIL: glibcs-ia64-linux-gnu check-compilers
FAIL: glibcs-sparcv8-linux-gnu-leon3 check
FAIL: glibcs-sparcv9-linux-gnu check
FAIL: glibcs-sparcv9-linux-gnu-disable-multi-arch check

All failures:

FAIL: glibcs-hppa-linux-gnu check-compilers
FAIL: glibcs-ia64-linux-gnu check-compilers
FAIL: glibcs-sparcv8-linux-gnu-leon3 check
FAIL: glibcs-sparcv9-linux-gnu check
FAIL: glibcs-sparcv9-linux-gnu-disable-multi-arch 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 (95385060771b0cac95a39320c44eca857fb177ae)
gcc: vcs-mainline (0f3bac474e8f6563a59f814ccf7609ced48b1157)
glibc: vcs-mainline (b3bee76c5f59498b9c189608f0a3132e2013fa1a)
gmp: 6.3.0 (6.3.0)
gnumach: vcs-mainline (c5f150653fd0642fdbd11b043dfbbbe473604570)
hurd: vcs-mainline (61fefecfd88282e1bb4dfdb4499518e33d18c6d8)
linux: 6.6 (6.6)
mig: vcs-mainline (a6a6afc285f8f4a1aadc8857ac980b62010ce004)
mpc: 1.3.1 (1.3.1)
mpfr: 4.2.1 (4.2.1)

                 reply	other threads:[~2023-12-09  7:05 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=170210554437.762733.12111047953858468607@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).