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 mainline glibcs 2022-10-08 05:58:35 build results Date: Sat, 8 Oct 2022 11:17:01 +0000 [thread overview] Message-ID: <166522782194.24665.5572905308330516870@build9-trusty-cs.sje.mentorg.com> (raw) All regressions: FAIL: glibcs-i686-linux-gnu-no-pie check FAIL: glibcs-loongarch64-linux-gnu-lp64s check-compilers FAIL: glibcs-x86_64-linux-gnu-no-pie check FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check All failures: FAIL: glibcs-i686-linux-gnu-no-pie check FAIL: glibcs-loongarch64-linux-gnu-lp64s check-compilers FAIL: glibcs-x86_64-linux-gnu-no-pie check FAIL: glibcs-x86_64-linux-gnu-x32-no-pie check All changed results: UNRESOLVED -> PASS: glibcs-arc-linux-gnu build UNRESOLVED -> PASS: glibcs-arc-linux-gnu check FAIL -> PASS: glibcs-arc-linux-gnu check-compilers UNRESOLVED -> PASS: glibcs-arc-linux-gnu configure UNRESOLVED -> PASS: glibcs-arc-linux-gnu install UNRESOLVED -> PASS: glibcs-arc-linux-gnu mkdir UNRESOLVED -> PASS: glibcs-arc-linux-gnu mkdir-lib UNRESOLVED -> PASS: glibcs-arc-linux-gnu rm UNRESOLVED -> PASS: glibcs-arc-linux-gnuhf build UNRESOLVED -> PASS: glibcs-arc-linux-gnuhf check FAIL -> PASS: glibcs-arc-linux-gnuhf check-compilers UNRESOLVED -> PASS: glibcs-arc-linux-gnuhf configure UNRESOLVED -> PASS: glibcs-arc-linux-gnuhf install UNRESOLVED -> PASS: glibcs-arc-linux-gnuhf mkdir UNRESOLVED -> PASS: glibcs-arc-linux-gnuhf mkdir-lib UNRESOLVED -> PASS: glibcs-arc-linux-gnuhf rm UNRESOLVED -> PASS: glibcs-arceb-linux-gnu build UNRESOLVED -> PASS: glibcs-arceb-linux-gnu check FAIL -> PASS: glibcs-arceb-linux-gnu check-compilers UNRESOLVED -> PASS: glibcs-arceb-linux-gnu configure UNRESOLVED -> PASS: glibcs-arceb-linux-gnu install UNRESOLVED -> PASS: glibcs-arceb-linux-gnu mkdir UNRESOLVED -> PASS: glibcs-arceb-linux-gnu mkdir-lib UNRESOLVED -> PASS: glibcs-arceb-linux-gnu rm Component versions for this build: binutils: vcs-mainline (4cbfd0daabd68516651ee37a19d0e24ca4789ea3) gcc: vcs-mainline (9ff6c33e2ec0d75958d3f19089519034e8f96a30) glibc: vcs-mainline (f9646d138f568ced95b29c20efdf902063c7ea96) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (e45542fbd6cbc0a815b0808f16cf4a8e87410f64) hurd: vcs-mainline (8bc29be6ce900f3e6c683d030fa69ca915fcd969) linux: 6.0 (6.0) mig: vcs-mainline (68b3d8fe3a9595b7a5cb2bb6bc5973ba26139704) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-10-08 11:17 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=166522782194.24665.5572905308330516870@build9-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).