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 2023-10-07 02:04:18 build results Date: Sat, 7 Oct 2023 04:33:56 +0000 [thread overview] Message-ID: <169665323655.3676438.4581414600637854715@build4-jammy-cs.sje.mentorg.com> (raw) All regressions: FAIL: glibcs-hppa-linux-gnu check-compilers FAIL: glibcs-i486-linux-gnu check-compilers FAIL: glibcs-i586-linux-gnu check-compilers FAIL: glibcs-i686-gnu check-compilers FAIL: glibcs-i686-linux-gnu check-compilers FAIL: glibcs-i686-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-i686-linux-gnu-no-pie check-compilers FAIL: glibcs-ia64-linux-gnu check-compilers FAIL: glibcs-x86_64-gnu check FAIL: glibcs-x86_64-linux-gnu check-compilers FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-x86_64-linux-gnu-enable-crypt check-compilers FAIL: glibcs-x86_64-linux-gnu-enable-fortify-source check-compilers FAIL: glibcs-x86_64-linux-gnu-minimal check-compilers FAIL: glibcs-x86_64-linux-gnu-no-pie check-compilers FAIL: glibcs-x86_64-linux-gnu-x32 check-compilers FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check-compilers All failures: FAIL: glibcs-hppa-linux-gnu check-compilers FAIL: glibcs-i486-linux-gnu check-compilers FAIL: glibcs-i586-linux-gnu check-compilers FAIL: glibcs-i686-gnu check-compilers FAIL: glibcs-i686-linux-gnu check-compilers FAIL: glibcs-i686-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-i686-linux-gnu-no-pie check-compilers FAIL: glibcs-ia64-linux-gnu check-compilers FAIL: glibcs-x86_64-gnu check FAIL: glibcs-x86_64-linux-gnu check-compilers FAIL: glibcs-x86_64-linux-gnu-disable-multi-arch check-compilers FAIL: glibcs-x86_64-linux-gnu-enable-crypt check-compilers FAIL: glibcs-x86_64-linux-gnu-enable-fortify-source check-compilers FAIL: glibcs-x86_64-linux-gnu-minimal check-compilers FAIL: glibcs-x86_64-linux-gnu-no-pie check-compilers FAIL: glibcs-x86_64-linux-gnu-x32 check-compilers FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check-compilers Component versions for this build: binutils: vcs-mainline (0f3efefb34f83236ec7d780747103a0b4f3fb6b1) gcc: vcs-mainline (ce658accc7beed19341b6847e6f257f08306a96e) glibc: vcs-mainline (a3c50bf46a1ca6d9d2b7d879176d345abf95a9de) gmp: 6.3.0 (6.3.0) gnumach: vcs-mainline (60c53f565454a6afd8f0b80d36d791d50653751d) hurd: vcs-mainline (34b3fbee22b63e65f403f87045faf705ab5b8531) linux: 6.5 (6.5) mig: vcs-mainline (b5a567954ce3b4d236b7a2375a6a00f3a4a853e8) mpc: 1.3.1 (1.3.1) mpfr: 4.2.1 (4.2.1)
reply other threads:[~2023-10-07 4:34 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=169665323655.3676438.4581414600637854715@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: 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).