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 2023-12-22 15:31:29 build results Date: Fri, 22 Dec 2023 18:28:34 +0000 [thread overview] Message-ID: <170326971421.979139.2610672321311436276@build3-jammy-cs.sje.mentorg.com> (raw) All failures: FAIL: glibcs-x86_64-gnu check-compilers Component versions for this build: binutils: vcs-2.41 (72a940c08470742b6cc3e3a810652cdb73d12d8c) gcc: vcs-12 (2f545b24e1022e1ad3795b3a9499358b9fc85cde) glibc: vcs-mainline (81be2a61dafc168327c1639e97b6dae128c7ccf3) gmp: 6.3.0 (6.3.0) gnumach: vcs-mainline (4541faab2ec63444e5afdb1aa17b0cb6180a3d55) hurd: vcs-mainline (6b494f5e7599ece2ca981472d690db3df3133bde) linux: 6.6 (6.6) mig: vcs-mainline (3b1fcb2b83bb26d43dc912884499345f561d0b6a) mpc: 1.3.1 (1.3.1) mpfr: 4.2.1 (4.2.1)
reply other threads:[~2023-12-22 18:44 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=170326971421.979139.2610672321311436276@build3-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).