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-12-14 16:09:21 build results Date: Wed, 14 Dec 2022 18:13:25 +0000 [thread overview] Message-ID: <167104160565.740110.7934632864973693595@build4-jammy-cs.sje.mentorg.com> (raw) All regressions: FAIL: compilers-m68k-linux-gnu-coldfire gcc build FAIL: compilers-m68k-linux-gnu-coldfire-soft glibc m68k-linux-gnu-coldfire-soft build All failures: FAIL: compilers-m68k-linux-gnu-coldfire gcc build FAIL: compilers-m68k-linux-gnu-coldfire-soft glibc m68k-linux-gnu-coldfire-soft build All changed results: UNRESOLVED -> PASS: compilers-aarch64-linux-gnu done UNRESOLVED -> PASS: compilers-aarch64-linux-gnu gcc build UNRESOLVED -> PASS: compilers-aarch64-linux-gnu gcc configure UNRESOLVED -> PASS: compilers-aarch64-linux-gnu gcc install UNRESOLVED -> PASS: compilers-aarch64-linux-gnu gcc mkdir UNRESOLVED -> PASS: compilers-aarch64-linux-gnu gcc rm FAIL -> PASS: compilers-aarch64-linux-gnu glibc aarch64-linux-gnu build UNRESOLVED -> PASS: compilers-aarch64-linux-gnu glibc aarch64-linux-gnu install UNRESOLVED -> PASS: compilers-aarch64-linux-gnu glibc aarch64-linux-gnu mkdir-lib UNRESOLVED -> PASS: compilers-aarch64_be-linux-gnu done UNRESOLVED -> PASS: compilers-aarch64_be-linux-gnu gcc build UNRESOLVED -> PASS: compilers-aarch64_be-linux-gnu gcc configure UNRESOLVED -> PASS: compilers-aarch64_be-linux-gnu gcc install UNRESOLVED -> PASS: compilers-aarch64_be-linux-gnu gcc mkdir UNRESOLVED -> PASS: compilers-aarch64_be-linux-gnu gcc rm FAIL -> PASS: compilers-aarch64_be-linux-gnu glibc aarch64_be-linux-gnu build UNRESOLVED -> PASS: compilers-aarch64_be-linux-gnu glibc aarch64_be-linux-gnu install UNRESOLVED -> PASS: compilers-aarch64_be-linux-gnu glibc aarch64_be-linux-gnu mkdir-lib Component versions for this build: binutils: vcs-mainline (5d80df4a109e7b648e324423a5fbc3c1ba02e816) gcc: vcs-mainline (330b9a8d87dd73e10539da618496ad4964fee26d) glibc: vcs-mainline (6fd504849de404aad59df5b198d3751b373a0154) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (3c26c30fd2a5bdec081384d45e42a7ea4e424846) hurd: vcs-mainline (c644533e2a8cd395997609f7e33b1e38c27e40f0) linux: 6.0 (6.0) mig: vcs-mainline (7063f0aefd8a8c3c8b610ef6168cddfb2141fa12) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-12-14 18:13 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=167104160565.740110.7934632864973693595@build4-jammy-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).