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 2022-03-09 19:23:49 build results
Date: Thu, 10 Mar 2022 00:37:47 +0000	[thread overview]
Message-ID: <164687266706.7971.4017946307185355582@build9-trusty-cs.sje.mentorg.com> (raw)

New regressions:

FAIL: compilers-powerpc-linux-gnu-soft gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imac-ilp32 gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32 gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32d gcc build
FAIL: compilers-s390x-linux-gnu gcc build

All regressions:

FAIL: compilers-powerpc-linux-gnu gcc build
FAIL: compilers-powerpc-linux-gnu-soft gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imac-ilp32 gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32 gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32d gcc build
FAIL: compilers-s390x-linux-gnu gcc build
FAIL: compilers-sh4-linux-gnu glibc sh4-linux-gnu build
FAIL: compilers-sh4eb-linux-gnu glibc sh4eb-linux-gnu build

All failures:

FAIL: compilers-powerpc-linux-gnu gcc build
FAIL: compilers-powerpc-linux-gnu-soft gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imac-ilp32 gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32 gcc build
FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32d gcc build
FAIL: compilers-s390x-linux-gnu gcc build
FAIL: compilers-sh4-linux-gnu glibc sh4-linux-gnu build
FAIL: compilers-sh4eb-linux-gnu glibc sh4eb-linux-gnu build

All changed results:

PASS -> UNRESOLVED: compilers-powerpc-linux-gnu-soft done
PASS -> FAIL: compilers-powerpc-linux-gnu-soft gcc build
PASS -> UNRESOLVED: compilers-powerpc-linux-gnu-soft gcc install
PASS -> UNRESOLVED: compilers-riscv32-linux-gnu-rv32imac-ilp32 done
PASS -> FAIL: compilers-riscv32-linux-gnu-rv32imac-ilp32 gcc build
PASS -> UNRESOLVED: compilers-riscv32-linux-gnu-rv32imac-ilp32 gcc install
PASS -> UNRESOLVED: compilers-riscv32-linux-gnu-rv32imafdc-ilp32 done
PASS -> FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32 gcc build
PASS -> UNRESOLVED: compilers-riscv32-linux-gnu-rv32imafdc-ilp32 gcc install
PASS -> UNRESOLVED: compilers-riscv32-linux-gnu-rv32imafdc-ilp32d done
PASS -> FAIL: compilers-riscv32-linux-gnu-rv32imafdc-ilp32d gcc build
PASS -> UNRESOLVED: compilers-riscv32-linux-gnu-rv32imafdc-ilp32d gcc install
PASS -> UNRESOLVED: compilers-s390x-linux-gnu done
PASS -> FAIL: compilers-s390x-linux-gnu gcc build
PASS -> UNRESOLVED: compilers-s390x-linux-gnu gcc install

Component versions for this build:

binutils: vcs-mainline (befb57e516c5c79324a0469c805a0d8693393ba7)
gcc: vcs-mainline (450526551dcb97b7c0513699d4333efb79b8b490)
glibc: vcs-mainline (edc696a73a7cb07b1aa68792a845a98d036ee7eb)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (6951d552749fe24d0c9514ac6efec2c09e567b8d)
hurd: vcs-mainline (866371cd8b06f20989eff1c58dff71535b3a0fa7)
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-03-10  0:37 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=164687266706.7971.4017946307185355582@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).