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 compilers 2022-05-10 23:05:50 build results Date: Wed, 11 May 2022 04:17:40 +0000 [thread overview] Message-ID: <165224266050.16796.2537616414541721335@build9-trusty-cs.sje.mentorg.com> (raw) All regressions: FAIL: compilers-sh4-linux-gnu glibc sh4-linux-gnu build FAIL: compilers-sh4eb-linux-gnu glibc sh4eb-linux-gnu build All failures: FAIL: compilers-sh4-linux-gnu glibc sh4-linux-gnu build FAIL: compilers-sh4eb-linux-gnu glibc sh4eb-linux-gnu build All changed results: UNRESOLVED -> PASS: compilers-arm-linux-gnueabi done FAIL -> PASS: compilers-arm-linux-gnueabi gcc build UNRESOLVED -> PASS: compilers-arm-linux-gnueabi gcc install UNRESOLVED -> PASS: compilers-arm-linux-gnueabihf done FAIL -> PASS: compilers-arm-linux-gnueabihf gcc build UNRESOLVED -> PASS: compilers-arm-linux-gnueabihf gcc install UNRESOLVED -> PASS: compilers-armeb-linux-gnueabi done FAIL -> PASS: compilers-armeb-linux-gnueabi gcc build UNRESOLVED -> PASS: compilers-armeb-linux-gnueabi gcc install UNRESOLVED -> PASS: compilers-armeb-linux-gnueabi-be8 done FAIL -> PASS: compilers-armeb-linux-gnueabi-be8 gcc build UNRESOLVED -> PASS: compilers-armeb-linux-gnueabi-be8 gcc install UNRESOLVED -> PASS: compilers-armeb-linux-gnueabihf done FAIL -> PASS: compilers-armeb-linux-gnueabihf gcc build UNRESOLVED -> PASS: compilers-armeb-linux-gnueabihf gcc install UNRESOLVED -> PASS: compilers-armeb-linux-gnueabihf-be8 done FAIL -> PASS: compilers-armeb-linux-gnueabihf-be8 gcc build UNRESOLVED -> PASS: compilers-armeb-linux-gnueabihf-be8 gcc install Component versions for this build: binutils: vcs-mainline (f8b786e2eddbbad9e9aa724038feb1ffcf7b2bd9) gcc: vcs-mainline (a4ad92fc4d0d0cdb003f4355a99132f556a06b0d) glibc: vcs-mainline (8162147872491bb5b48e91543b19c49a29ae6b6d) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (96b925573917679a5899a74c1c279c734e614211) hurd: vcs-mainline (88ee4ae44bd64e869bca79d0a6c6e6d4577b7170) linux: 5.17 (5.17) mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-05-11 4: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=165224266050.16796.2537616414541721335@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).