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-09-13 18:37:00 build results Date: Wed, 13 Sep 2023 21:33:40 +0000 [thread overview] Message-ID: <169464082085.147046.17891212398756480092@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 (6ffa5a420a0ce533feb6bc09f6f76bac9e3930bd) gcc: vcs-12 (1bfe036184e1b5e9bd1cecb94045da0f073657f9) glibc: vcs-mainline (bd77dd7e73e3530203be1c52c8a29d08270cb25d) gmp: 6.3.0 (6.3.0) gnumach: vcs-mainline (f292a4c38923278ab69bfaccbc67e0ad6b13484d) hurd: vcs-mainline (0687986bb30a3c550ce056fc1170712c90188257) linux: 6.5 (6.5) mig: vcs-mainline (d9a36da6d785844139d291b37f80fbe087b2b59e) mpc: 1.3.1 (1.3.1) mpfr: 4.2.1 (4.2.1)
reply other threads:[~2023-09-13 21:33 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=169464082085.147046.17891212398756480092@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).