public inbox for
help / color / mirror / Atom feed
From: Joseph Myers <>
To: <>
Subject: GCC 11 glibcs 2022-09-01 06:09:53 build results
Date: Thu, 1 Sep 2022 10:01:49 +0000	[thread overview]
Message-ID: <> (raw)

All regressions:

FAIL: glibcs-i686-linux-gnu-no-pie 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-compilers
FAIL: glibcs-loongarch64-linux-gnu-lp64s check-compilers
FAIL: glibcs-x86_64-linux-gnu-no-pie check
FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check

All changed results:

(New test) -> UNRESOLVED: glibcs-loongarch64-linux-gnu-lp64s build
(New test) -> UNRESOLVED: glibcs-loongarch64-linux-gnu-lp64s check
(New test) -> FAIL: glibcs-loongarch64-linux-gnu-lp64s check-compilers
(New test) -> PASS: glibcs-loongarch64-linux-gnu-lp64s cleanup
(New test) -> UNRESOLVED: glibcs-loongarch64-linux-gnu-lp64s configure
(New test) -> UNRESOLVED: glibcs-loongarch64-linux-gnu-lp64s install
(New test) -> UNRESOLVED: glibcs-loongarch64-linux-gnu-lp64s mkdir
(New test) -> UNRESOLVED: glibcs-loongarch64-linux-gnu-lp64s mkdir-lib
(New test) -> UNRESOLVED: glibcs-loongarch64-linux-gnu-lp64s rm
(New test) -> PASS: glibcs-loongarch64-linux-gnu-lp64s save-logs

Component versions for this build:

binutils: vcs-2.39 (6995ff43693f4013942223267cfe0609272fc7fd)
gcc: vcs-11 (deb44cd0b27c3b82b73721123ce59470876cb175)
glibc: vcs-mainline (930993921f2f381b545ea1b1f2d9c534b2b72b08)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (66775cd2279be8e81269c06575c836900aa64793)
hurd: vcs-mainline (da8d2ba4b61a7d6b25f5b2215447795f2b9badf9)
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-01 10:01 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).