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-12-01 19:11:32 build results
Date: Fri, 1 Dec 2023 21:22:04 +0000	[thread overview]
Message-ID: <170146572442.671994.8270125075522503658@build4-jammy-cs.sje.mentorg.com> (raw)

All regressions:

FAIL: compilers-hppa-linux-gnu glibc hppa-linux-gnu build
FAIL: compilers-i686-gnu glibc i686-gnu build
FAIL: compilers-ia64-linux-gnu glibc ia64-linux-gnu build

All failures:

FAIL: compilers-hppa-linux-gnu glibc hppa-linux-gnu build
FAIL: compilers-i686-gnu glibc i686-gnu build
FAIL: compilers-ia64-linux-gnu glibc ia64-linux-gnu build

All changed results:

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

Component versions for this build:

binutils: vcs-mainline (c6f7f9c80c3b92c6d877214d38aaef141adc5b93)
gcc: vcs-mainline (b8edb812ff4934c609fdfafe2e1c7f932bc18305)
glibc: vcs-mainline (4e16d89866e660426438238a47c2345bdc47dd97)
gmp: 6.3.0 (6.3.0)
gnumach: vcs-mainline (6e0f722df45f6c261f250a8814458e19c2bed550)
hurd: vcs-mainline (5f25b24d6c6170cc366d9b71f99d741c4cfbc857)
linux: 6.6 (6.6)
mig: vcs-mainline (b5a567954ce3b4d236b7a2375a6a00f3a4a853e8)
mpc: 1.3.1 (1.3.1)
mpfr: 4.2.1 (4.2.1)

                 reply	other threads:[~2023-12-01 21:22 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=170146572442.671994.8270125075522503658@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).