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-02-09 22:18:03 build results Date: Thu, 10 Feb 2022 03:34:29 +0000 [thread overview] Message-ID: <164446406984.28538.4929294887356334790@build9-trusty-cs.sje.mentorg.com> (raw) All regressions: FAIL: glibcs-arc-linux-gnu check-compilers FAIL: glibcs-arc-linux-gnuhf check-compilers FAIL: glibcs-arceb-linux-gnu check-compilers FAIL: glibcs-hppa-linux-gnu check FAIL: glibcs-microblaze-linux-gnu check FAIL: glibcs-microblazeel-linux-gnu check FAIL: glibcs-s390x-linux-gnu-O3 check FAIL: glibcs-sh4-linux-gnu check-compilers FAIL: glibcs-sh4eb-linux-gnu check-compilers FAIL: glibcs-sparcv8-linux-gnu-leon3 check FAIL: glibcs-sparcv9-linux-gnu check FAIL: glibcs-sparcv9-linux-gnu-disable-multi-arch check All failures: FAIL: glibcs-arc-linux-gnu check-compilers FAIL: glibcs-arc-linux-gnuhf check-compilers FAIL: glibcs-arceb-linux-gnu check-compilers FAIL: glibcs-hppa-linux-gnu check FAIL: glibcs-microblaze-linux-gnu check FAIL: glibcs-microblazeel-linux-gnu check FAIL: glibcs-s390x-linux-gnu-O3 check FAIL: glibcs-sh4-linux-gnu check-compilers FAIL: glibcs-sh4eb-linux-gnu check-compilers FAIL: glibcs-sparcv8-linux-gnu-leon3 check FAIL: glibcs-sparcv9-linux-gnu check FAIL: glibcs-sparcv9-linux-gnu-disable-multi-arch check All changed results: UNRESOLVED -> PASS: glibcs-or1k-linux-gnu-soft build UNRESOLVED -> PASS: glibcs-or1k-linux-gnu-soft check FAIL -> PASS: glibcs-or1k-linux-gnu-soft check-compilers UNRESOLVED -> PASS: glibcs-or1k-linux-gnu-soft configure UNRESOLVED -> PASS: glibcs-or1k-linux-gnu-soft install UNRESOLVED -> PASS: glibcs-or1k-linux-gnu-soft mkdir UNRESOLVED -> PASS: glibcs-or1k-linux-gnu-soft mkdir-lib UNRESOLVED -> PASS: glibcs-or1k-linux-gnu-soft rm Component versions for this build: binutils: vcs-mainline (0f38fd87eaea358d11dd9a9ca4d15176fc23ed77) gcc: vcs-mainline (83d7e720cd1d075312e798c4ebd2e093f03465fb) glibc: vcs-mainline (9e94f57484a2aba0fe67ea2059b5843f651887c2) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (afa3aaefb317f9b7b5691cb15f97998389d8ed43) hurd: vcs-mainline (f31e025c650ec2666a4be76cff31d24a9944b7c1) linux: 5.16 (5.16) mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-02-10 3:34 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=164446406984.28538.4929294887356334790@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).