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 11 compilers 2023-01-19 19:05:57 build results
Date: Thu, 19 Jan 2023 20:48:48 +0000	[thread overview]
Message-ID: <167416132832.2521879.6713565418873270778@build2-jammy-cs.sje.mentorg.com> (raw)

New regressions:

FAIL: compilers-i686-gnu glibc i686-gnu build

All regressions:

FAIL: compilers-i686-gnu glibc i686-gnu build

All failures:

FAIL: compilers-i686-gnu glibc i686-gnu build
FAIL: compilers-loongarch64-linux-gnu-lp64d gcc-first build
FAIL: compilers-loongarch64-linux-gnu-lp64s gcc-first build

All changed results:

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

Component versions for this build:

binutils: vcs-2.39 (87cb95ba8c4d86de23b6ba694a126995a17c5fcd)
gcc: vcs-11 (5f30fae901cc442829350677519e534d41e758e9)
glibc: vcs-mainline (103a469dc7755fd9e8ccf362f3dd4c55dc761908)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (8d30c12342c1cafa7c02ecc00244f57cb39eb148)
hurd: vcs-mainline (bf721cfb73ffcf887d4e33a9338789bd56281f79)
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-19 20:48 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=167416132832.2521879.6713565418873270778@build2-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).