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 compilers 2023-02-08 01:09:28 build results
Date: Wed, 8 Feb 2023 03:13:07 +0000	[thread overview]
Message-ID: <167582598720.3290776.10982264853724107025@build4-jammy-cs.sje.mentorg.com> (raw)

New regressions:

FAIL: compilers-s390x-linux-gnu glibc s390x-linux-gnu build

All regressions:

FAIL: compilers-m68k-linux-gnu-coldfire gcc build
FAIL: compilers-m68k-linux-gnu-coldfire-soft glibc m68k-linux-gnu-coldfire-soft build
FAIL: compilers-s390x-linux-gnu glibc s390x-linux-gnu build

All failures:

FAIL: compilers-m68k-linux-gnu-coldfire gcc build
FAIL: compilers-m68k-linux-gnu-coldfire-soft glibc m68k-linux-gnu-coldfire-soft build
FAIL: compilers-s390x-linux-gnu glibc s390x-linux-gnu build

All changed results:

PASS -> UNRESOLVED: compilers-s390x-linux-gnu done
PASS -> UNRESOLVED: compilers-s390x-linux-gnu gcc build
PASS -> UNRESOLVED: compilers-s390x-linux-gnu gcc configure
PASS -> UNRESOLVED: compilers-s390x-linux-gnu gcc install
PASS -> UNRESOLVED: compilers-s390x-linux-gnu gcc mkdir
PASS -> UNRESOLVED: compilers-s390x-linux-gnu gcc rm
PASS -> UNRESOLVED: compilers-s390x-linux-gnu glibc s390-linux-gnu build
PASS -> UNRESOLVED: compilers-s390x-linux-gnu glibc s390-linux-gnu configure
PASS -> UNRESOLVED: compilers-s390x-linux-gnu glibc s390-linux-gnu install
PASS -> UNRESOLVED: compilers-s390x-linux-gnu glibc s390-linux-gnu mkdir
PASS -> UNRESOLVED: compilers-s390x-linux-gnu glibc s390-linux-gnu mkdir-lib
PASS -> UNRESOLVED: compilers-s390x-linux-gnu glibc s390-linux-gnu rm
PASS -> FAIL: compilers-s390x-linux-gnu glibc s390x-linux-gnu build
PASS -> UNRESOLVED: compilers-s390x-linux-gnu glibc s390x-linux-gnu install
PASS -> UNRESOLVED: compilers-s390x-linux-gnu glibc s390x-linux-gnu mkdir-lib

Component versions for this build:

binutils: vcs-mainline (4170bc7ea846a14485e4729f1e2d707a04035c6f)
gcc: vcs-mainline (8f3b85efbf549b19db4026e0ef7f4461db8cdb25)
glibc: vcs-mainline (67c37737ed474d25fd4dc535dfd822c426e6b971)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (ee5f05310f42a09fa274a3229ff840b639e93a1a)
hurd: vcs-mainline (b7287f6c4830d2957645abb3217f46489dc7bea3)
linux: 6.1 (6.1)
mig: vcs-mainline (d76280e4fc71265b88bce2bdaf25b3be846fc6b2)
mpc: 1.3.1 (1.3.1)
mpfr: 4.2.0 (4.2.0)

                 reply	other threads:[~2023-02-08  3:13 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=167582598720.3290776.10982264853724107025@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).