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-08-29 03:59:50 build results Date: Mon, 29 Aug 2022 08:55:17 +0000 [thread overview] Message-ID: <166176331701.8266.7420307472158940088@build9-trusty-cs.sje.mentorg.com> (raw) New regressions: FAIL: glibcs-i686-gnu check-compilers All regressions: FAIL: glibcs-i686-gnu check-compilers FAIL: glibcs-i686-linux-gnu-no-pie check FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers FAIL: glibcs-powerpc64-linux-gnu check-compilers FAIL: glibcs-powerpc64le-linux-gnu check-compilers FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-x86_64-linux-gnu-no-pie check FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check All failures: FAIL: glibcs-i686-gnu check-compilers FAIL: glibcs-i686-linux-gnu-no-pie check FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers FAIL: glibcs-powerpc64-linux-gnu check-compilers FAIL: glibcs-powerpc64le-linux-gnu check-compilers FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-x86_64-linux-gnu-no-pie check FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check All changed results: PASS -> UNRESOLVED: glibcs-i686-gnu build PASS -> UNRESOLVED: glibcs-i686-gnu check PASS -> FAIL: glibcs-i686-gnu check-compilers PASS -> UNRESOLVED: glibcs-i686-gnu configure PASS -> UNRESOLVED: glibcs-i686-gnu install PASS -> UNRESOLVED: glibcs-i686-gnu mkdir PASS -> UNRESOLVED: glibcs-i686-gnu mkdir-lib PASS -> UNRESOLVED: glibcs-i686-gnu rm Component versions for this build: binutils: vcs-mainline (6f6f5b0adc9efd103c434fd316e8c880a259775d) gcc: vcs-mainline (1ae1325f24cea1698b56e4299d95446a1f7b90a2) glibc: vcs-mainline (cb033e6b0ca7b8873cd00687ffd1828038a595d3) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (66775cd2279be8e81269c06575c836900aa64793) hurd: vcs-mainline (edcbe160f1038e5d17898f36866e91bebf15b87a) 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-08-29 8:55 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=166176331701.8266.7420307472158940088@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: linkBe 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).