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-11-11 19:01:32 build results Date: Sat, 12 Nov 2022 00:18:36 +0000 [thread overview] Message-ID: <166821231663.9193.15389545148290755996@build9-trusty-cs.sje.mentorg.com> (raw) New regressions: FAIL: glibcs-powerpc64le-linux-gnu check-compilers FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers All regressions: FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers FAIL: glibcs-powerpc64le-linux-gnu check-compilers FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers All failures: FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers FAIL: glibcs-powerpc64le-linux-gnu check-compilers FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers All changed results: PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu build PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu check PASS -> FAIL: glibcs-powerpc64le-linux-gnu check-compilers PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu configure PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu install PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu mkdir PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu mkdir-lib PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu rm PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch build PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch check PASS -> FAIL: glibcs-powerpc64le-linux-gnu-disable-multi-arch check-compilers PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch configure PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch install PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch mkdir PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch mkdir-lib PASS -> UNRESOLVED: glibcs-powerpc64le-linux-gnu-disable-multi-arch rm Component versions for this build: binutils: vcs-mainline (1e5ccb9c5ff4fd8ade4a8694676f99f4abf2d679) gcc: vcs-mainline (02698e21de26c7d4217f856ee64436148e0aede7) glibc: vcs-mainline (22a46dee24351fd5f4f188ad80554cad79c82524) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (356d54992ab479e4709b3afce222759bfb3e0989) hurd: vcs-mainline (998e9774781ac360d5d3704845c0e24d44c940f5) linux: 6.0 (6.0) mig: vcs-mainline (3902cb2fcae6e2028252b5d2016bf0e99ed74980) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-11-12 0:18 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=166821231663.9193.15389545148290755996@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).