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-02-17 13:22:35 build results
Date: Fri, 17 Feb 2023 15:39:07 +0000	[thread overview]
Message-ID: <167664834748.1151654.8188387365727297738@build4-jammy-cs.sje.mentorg.com> (raw)

All regressions:

FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers
FAIL: glibcs-s390-linux-gnu check-compilers
FAIL: glibcs-s390x-linux-gnu check-compilers
FAIL: glibcs-s390x-linux-gnu-O3 check-compilers

All failures:

FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers
FAIL: glibcs-s390-linux-gnu check-compilers
FAIL: glibcs-s390x-linux-gnu check-compilers
FAIL: glibcs-s390x-linux-gnu-O3 check-compilers

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 (5f497256bee624f0fa470949aa41534093bc5b25)
gcc: vcs-mainline (f978585c2939691176ad8d3fa9c2e4e91ed18bf4)
glibc: vcs-mainline (26c176950909d60ac2a392cf9fce70eabd75f79e)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (1b8d96d72b6978b6d2b0f734f1307d6c054e1a0d)
hurd: vcs-mainline (b8bcd4eb1438721f6a52bfd1e458307d4e105d89)
linux: 6.1 (6.1)
mig: vcs-mainline (a391c8f0eef8573fd6b99e6cd264a5f2caa539cb)
mpc: 1.3.1 (1.3.1)
mpfr: 4.2.0 (4.2.0)

                 reply	other threads:[~2023-02-17 15:39 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=167664834748.1151654.8188387365727297738@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).