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-08-24 13:54:46 build results Date: Wed, 24 Aug 2022 19:18:58 +0000 [thread overview] Message-ID: <166136873853.20849.4181150581856880354@build9-trusty-cs.sje.mentorg.com> (raw) New regressions: FAIL: compilers-loongarch64-linux-gnu-lp64d gcc-first build All regressions: FAIL: compilers-loongarch64-linux-gnu-lp64d gcc-first build FAIL: compilers-m68k-linux-gnu-coldfire-soft glibc m68k-linux-gnu-coldfire-soft build All failures: FAIL: compilers-loongarch64-linux-gnu-lp64d gcc-first build FAIL: compilers-m68k-linux-gnu-coldfire-soft glibc m68k-linux-gnu-coldfire-soft build All changed results: PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d done PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d gcc build PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d gcc configure PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d gcc install PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d gcc mkdir PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d gcc rm PASS -> FAIL: compilers-loongarch64-linux-gnu-lp64d gcc-first build PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d gcc-first install PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d build PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d configure PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d install PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d mkdir PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d mkdir-lib PASS -> UNRESOLVED: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d rm Component versions for this build: binutils: vcs-mainline (70175292616118bad315296ba6180f375326bb6c) gcc: vcs-mainline (6d1f144b3e6e3761375bea657718f58fb720fb44) glibc: vcs-mainline (06e4033c83276ed349d315bfbf651be56c3e2954) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (f2626beb39dc416ceebfa35076d89cd291e2b903) hurd: vcs-mainline (772e292c2d47e9d93455e3c87ae0209a58a3da67) linux: 5.19 (5.19) mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-08-24 19:19 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=166136873853.20849.4181150581856880354@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).