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-09 19:38:23 build results Date: Fri, 9 Jun 2023 21:54:32 +0000 [thread overview] Message-ID: <168634767224.2702225.13693373379837061327@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 (1720c590f36a2e2b807fc059e696ca61899b7b0a) gcc: vcs-12 (3b09a5453114fee10b0f0984793ce968503dbea7) glibc: vcs-mainline (5e8d1b0328a850c229146f40e18848728b104583) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (ee2e9072964ce1615c9059a6141200244f9f9119) hurd: vcs-mainline (7ae31255799b7aad9cf897343ff65cc26fab07cf) linux: 6.3 (6.3) mig: vcs-mainline (f519e6e262b4f0f3cf7f2ffd8f9634c9f05d6ed4) mpc: 1.3.1 (1.3.1) mpfr: 4.2.0 (4.2.0)
reply other threads:[~2023-06-09 21:54 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=168634767224.2702225.13693373379837061327@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).