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-07-05 19:21:06 build results Date: Wed, 5 Jul 2023 21:39:24 +0000 [thread overview] Message-ID: <168859316404.828930.2827930836657020326@build3-jammy-cs.sje.mentorg.com> (raw) All failures: FAIL: glibcs-x86_64-gnu check-compilers All changed results: (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source build (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source check (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source check-compilers (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source cleanup (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source configure (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source install (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source mkdir (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source mkdir-lib (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source rm (New test) -> PASS: glibcs-x86_64-linux-gnu-enable-fortify-source save-logs Component versions for this build: binutils: vcs-2.40 (99d0971e801a0a92412cccbf8bce80da26a646b5) gcc: vcs-12 (6c072ec50158d6ca9134d4778ad60bb452b1f664) glibc: vcs-mainline (02261d1bd930b50e9166086462dca885e9847826) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (cab23fb54d10843158e874d87dd3725ddbb2b4db) hurd: vcs-mainline (7abafc25f97897fd61762c45f8729fa952aa822c) 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-07-05 21:39 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=168859316404.828930.2827930836657020326@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).