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 12 glibcs 2022-09-30 08:59:58 build results
Date: Fri, 30 Sep 2022 12:28:40 +0000	[thread overview]
Message-ID: <166454091998.130259.16716958327340574427@build6-trusty-cs.sje.mentorg.com> (raw)

New regressions:

FAIL: glibcs-loongarch64-linux-gnu-lp64d check
FAIL: glibcs-loongarch64-linux-gnu-lp64s check

All regressions:

FAIL: glibcs-i686-linux-gnu-no-pie check
FAIL: glibcs-loongarch64-linux-gnu-lp64d check
FAIL: glibcs-loongarch64-linux-gnu-lp64s check
FAIL: glibcs-x86_64-linux-gnu-no-pie check
FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check

All failures:

FAIL: glibcs-i686-linux-gnu-no-pie check
FAIL: glibcs-loongarch64-linux-gnu-lp64d check
FAIL: glibcs-loongarch64-linux-gnu-lp64s check
FAIL: glibcs-x86_64-linux-gnu-no-pie check
FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check

All changed results:

PASS -> FAIL: glibcs-loongarch64-linux-gnu-lp64d check
PASS -> FAIL: glibcs-loongarch64-linux-gnu-lp64s check

Component versions for this build:

binutils: vcs-2.39 (51bb603748c8141e56c0031ae103b0d602e4dbd6)
gcc: vcs-12 (6a59baca1f2a6b42021d194006f09edd6ba26ce8)
glibc: vcs-mainline (8b10727a9af3e2aa4b27dff0116bb8d3c9afce3d)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (e45542fbd6cbc0a815b0808f16cf4a8e87410f64)
hurd: vcs-mainline (8bc29be6ce900f3e6c683d030fa69ca915fcd969)
linux: 5.19 (5.19)
mig: vcs-mainline (68b3d8fe3a9595b7a5cb2bb6bc5973ba26139704)
mpc: 1.2.1 (1.2.1)
mpfr: 4.1.0 (4.1.0)

                 reply	other threads:[~2022-09-30 12:28 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=166454091998.130259.16716958327340574427@build6-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).