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-06-29 00:07:12 build results Date: Thu, 29 Jun 2023 02:23:02 +0000 [thread overview] Message-ID: <168800538205.4096581.16324660841385781586@build3-jammy-cs.sje.mentorg.com> (raw) All failures: FAIL: glibcs-x86_64-gnu check-compilers Component versions for this build: binutils: vcs-2.40 (28cb7cd2300df920d6e676af840a7e7970f0d7e6) gcc: vcs-12 (ee3bb7cb5d2ecfc64adcfd61afb390e72cc08661) glibc: vcs-mainline (1a21693e16a3f3d10f41c486b97fbecb53dd2087) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (d5464d531aaba049a3e734adb80fb0bfd28093a7) hurd: vcs-mainline (b17b96b9dd665687104c39c0d8559319c279d217) linux: 6.4 (6.4) mig: vcs-mainline (d9a36da6d785844139d291b37f80fbe087b2b59e) mpc: 1.3.1 (1.3.1) mpfr: 4.2.0 (4.2.0)
reply other threads:[~2023-06-29 2:23 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=168800538205.4096581.16324660841385781586@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).