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 2022-06-18 06:43:01 build results Date: Sat, 18 Jun 2022 10:02:41 +0000 [thread overview] Message-ID: <165554656182.114098.1666008993516451027@build6-trusty-cs.sje.mentorg.com> (raw) All failures: FAIL: glibcs-sh4-linux-gnu check-compilers FAIL: glibcs-sh4eb-linux-gnu check-compilers All changed results: FAIL -> PASS: glibcs-i686-gnu build UNRESOLVED -> PASS: glibcs-i686-gnu check UNRESOLVED -> PASS: glibcs-i686-gnu install UNRESOLVED -> PASS: glibcs-i686-gnu mkdir-lib FAIL -> PASS: glibcs-i686-linux-gnu build UNRESOLVED -> PASS: glibcs-i686-linux-gnu check UNRESOLVED -> PASS: glibcs-i686-linux-gnu install UNRESOLVED -> PASS: glibcs-i686-linux-gnu mkdir-lib FAIL -> PASS: glibcs-i686-linux-gnu-no-pie build UNRESOLVED -> PASS: glibcs-i686-linux-gnu-no-pie check UNRESOLVED -> PASS: glibcs-i686-linux-gnu-no-pie install UNRESOLVED -> PASS: glibcs-i686-linux-gnu-no-pie mkdir-lib Component versions for this build: binutils: vcs-2.38 (614000f9d7b1ce981f5210a34788c8905243ec81) gcc: vcs-12 (4b06b7304066fb1016e017d15e189f2e745dceae) glibc: vcs-mainline (e5446dfea11e969212939197b606424a718d9b65) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (151dfe9971ac2bd4d9afb440f2a5b2a4f9a58969) hurd: vcs-mainline (88ee4ae44bd64e869bca79d0a6c6e6d4577b7170) linux: 5.18 (5.18) mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-06-18 10:02 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=165554656182.114098.1666008993516451027@build6-trusty-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).