GCC mainline glibcs 2022-02-01 11:30:44 build results

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 2022-02-01 11:30:44 build results
Date: Tue, 1 Feb 2022 16:15:00 +0000	[thread overview]
Message-ID: <164373210021.6673.9492646820920115972@build9-trusty-cs.sje.mentorg.com> (raw)

All regressions:

FAIL: glibcs-arc-linux-gnu check-compilers
FAIL: glibcs-arc-linux-gnuhf check-compilers
FAIL: glibcs-arceb-linux-gnu check-compilers
FAIL: glibcs-hppa-linux-gnu check
FAIL: glibcs-microblaze-linux-gnu check
FAIL: glibcs-microblazeel-linux-gnu check
FAIL: glibcs-or1k-linux-gnu-soft check-compilers
FAIL: glibcs-s390x-linux-gnu-O3 check
FAIL: glibcs-sh4-linux-gnu check-compilers
FAIL: glibcs-sh4eb-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-arc-linux-gnu check-compilers
FAIL: glibcs-arc-linux-gnuhf check-compilers
FAIL: glibcs-arceb-linux-gnu check-compilers
FAIL: glibcs-hppa-linux-gnu check
FAIL: glibcs-microblaze-linux-gnu check
FAIL: glibcs-microblazeel-linux-gnu check
FAIL: glibcs-or1k-linux-gnu-soft check-compilers
FAIL: glibcs-s390x-linux-gnu-O3 check
FAIL: glibcs-sh4-linux-gnu check-compilers
FAIL: glibcs-sh4eb-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:

FAIL -> PASS: glibcs-csky-linux-gnuabiv2 check
FAIL -> PASS: glibcs-csky-linux-gnuabiv2-soft check
FAIL -> PASS: glibcs-i486-linux-gnu check
FAIL -> PASS: glibcs-i586-linux-gnu check
FAIL -> PASS: glibcs-i686-gnu check
FAIL -> PASS: glibcs-i686-linux-gnu check
FAIL -> PASS: glibcs-i686-linux-gnu-disable-multi-arch check
FAIL -> PASS: glibcs-i686-linux-gnu-no-pie check
FAIL -> PASS: glibcs-m68k-linux-gnu check
FAIL -> PASS: glibcs-m68k-linux-gnu-coldfire check
FAIL -> PASS: glibcs-m68k-linux-gnu-coldfire-soft check
FAIL -> PASS: glibcs-mips-linux-gnu check
FAIL -> PASS: glibcs-mips-linux-gnu-nan2008 check
FAIL -> PASS: glibcs-mips-linux-gnu-nan2008-soft check
FAIL -> PASS: glibcs-mips-linux-gnu-soft check
FAIL -> PASS: glibcs-mips64-linux-gnu-n32 check
FAIL -> PASS: glibcs-mips64-linux-gnu-n32-nan2008 check
FAIL -> PASS: glibcs-mips64-linux-gnu-n32-nan2008-soft check
FAIL -> PASS: glibcs-mips64-linux-gnu-n32-soft check
FAIL -> PASS: glibcs-mips64el-linux-gnu-n32 check
FAIL -> PASS: glibcs-mips64el-linux-gnu-n32-nan2008 check
FAIL -> PASS: glibcs-mips64el-linux-gnu-n32-nan2008-soft check
FAIL -> PASS: glibcs-mips64el-linux-gnu-n32-soft check
FAIL -> PASS: glibcs-mipsel-linux-gnu check
FAIL -> PASS: glibcs-mipsel-linux-gnu-nan2008 check
FAIL -> PASS: glibcs-mipsel-linux-gnu-nan2008-soft check
FAIL -> PASS: glibcs-mipsel-linux-gnu-soft check
FAIL -> PASS: glibcs-mipsisa32r6el-linux-gnu check
FAIL -> PASS: glibcs-mipsisa64r6el-linux-gnu-n32 check
FAIL -> PASS: glibcs-nios2-linux-gnu check
FAIL -> PASS: glibcs-powerpc-linux-gnu check
FAIL -> PASS: glibcs-powerpc-linux-gnu-power4 check
FAIL -> PASS: glibcs-powerpc-linux-gnu-soft check
FAIL -> PASS: glibcs-riscv32-linux-gnu-rv32imac-ilp32 check
FAIL -> PASS: glibcs-riscv32-linux-gnu-rv32imafdc-ilp32 check
FAIL -> PASS: glibcs-riscv32-linux-gnu-rv32imafdc-ilp32d check
FAIL -> PASS: glibcs-s390-linux-gnu check
FAIL -> PASS: glibcs-sh3-linux-gnu check
FAIL -> PASS: glibcs-sh3eb-linux-gnu check
FAIL -> PASS: glibcs-sh4-linux-gnu-soft check
FAIL -> PASS: glibcs-sh4eb-linux-gnu-soft check
FAIL -> PASS: glibcs-x86_64-linux-gnu-x32 check
FAIL -> PASS: glibcs-x86_64-linux-gnu-x32-no-pie check

Component versions for this build:

binutils: vcs-mainline (e327c35ef5768789d3ba41a629f178f5eec32790)
gcc: vcs-mainline (1bb52662574f6c98de48a5db8c180786e4a53039)
glibc: vcs-mainline (3fb18fd80c5900cc82748f3320b30516c57d24da)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (fb3cc15b1662f00c11d889584f6bc8e3a853c947)
hurd: vcs-mainline (f94e6284aa777ab7b63374759b35e0d8219e3d4d)
linux: 5.16 (5.16)
mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f)
mpc: 1.2.1 (1.2.1)
mpfr: 4.1.0 (4.1.0)

                 reply	other threads:[~2022-02-01 16:15 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=164373210021.6673.9492646820920115972@build9-trusty-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).