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-20 14:24:45 build results Date: Sun, 20 Nov 2022 19:35:11 +0000 [thread overview] Message-ID: <166897291109.2283.10648459215637467523@build9-trusty-cs.sje.mentorg.com> (raw) All regressions: FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers FAIL: glibcs-riscv64-linux-gnu-rv64imac-lp64 check-compilers FAIL: glibcs-riscv64-linux-gnu-rv64imafdc-lp64 check-compilers FAIL: glibcs-riscv64-linux-gnu-rv64imafdc-lp64d check-compilers FAIL: glibcs-sparc64-linux-gnu check FAIL: glibcs-sparc64-linux-gnu-disable-multi-arch check All failures: FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers FAIL: glibcs-riscv64-linux-gnu-rv64imac-lp64 check-compilers FAIL: glibcs-riscv64-linux-gnu-rv64imafdc-lp64 check-compilers FAIL: glibcs-riscv64-linux-gnu-rv64imafdc-lp64d check-compilers FAIL: glibcs-sparc64-linux-gnu check FAIL: glibcs-sparc64-linux-gnu-disable-multi-arch check Component versions for this build: binutils: vcs-mainline (abad6c11d03e17a5fef9d6fff5e58f8a288620f0) gcc: vcs-mainline (6d82e0fea5f988e829912aaa70a9964a81ad4e5e) glibc: vcs-mainline (a9acb7b39ed21386142b963aeecc35e0b468c0de) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (a0b853a5a06e615d0f1a186a2add5ff87b913f55) hurd: vcs-mainline (12a94cd0fc3f399e932f5529d5ab6b40f0afa791) linux: 6.0 (6.0) mig: vcs-mainline (f51fc836c5b690f5448e76196dd40bdb55957a11) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-11-20 19:35 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=166897291109.2283.10648459215637467523@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).