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-10 21:16:05 build results
Date: Tue, 10 Jan 2023 23:30:23 +0000	[thread overview]
Message-ID: <167339342306.704919.8775097992190890145@build4-jammy-cs.sje.mentorg.com> (raw)

New regressions:

FAIL: glibcs-csky-linux-gnuabiv2 check-compilers

All regressions:

FAIL: glibcs-csky-linux-gnuabiv2 check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers

All failures:

FAIL: glibcs-csky-linux-gnuabiv2 check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers
FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers

All changed results:

PASS -> UNRESOLVED: glibcs-csky-linux-gnuabiv2 build
PASS -> UNRESOLVED: glibcs-csky-linux-gnuabiv2 check
PASS -> FAIL: glibcs-csky-linux-gnuabiv2 check-compilers
PASS -> UNRESOLVED: glibcs-csky-linux-gnuabiv2 configure
PASS -> UNRESOLVED: glibcs-csky-linux-gnuabiv2 install
PASS -> UNRESOLVED: glibcs-csky-linux-gnuabiv2 mkdir
PASS -> UNRESOLVED: glibcs-csky-linux-gnuabiv2 mkdir-lib
PASS -> UNRESOLVED: glibcs-csky-linux-gnuabiv2 rm

Component versions for this build:

binutils: vcs-mainline (8ec0b0b5df0ebe28c32900afc7ae8ff22b21f381)
gcc: vcs-mainline (e9a39ad7936815980013605b052b12425d56ead8)
glibc: vcs-mainline (57f4a850c84a0545dec9aea4242241d2b19fa6af)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (80a022e8e7738e2c616ac793f53c6b5005300101)
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-10 23:30 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=167339342306.704919.8775097992190890145@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).