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-10-21 05:10:19 build results Date: Fri, 21 Oct 2022 10:47:33 +0000 [thread overview] Message-ID: <166634925295.1234.13050252507144259126@build9-trusty-cs.sje.mentorg.com> (raw) New regressions: FAIL: compilers-m68k-linux-gnu-coldfire gcc build FAIL: compilers-m68k-linux-gnu-coldfire-soft gcc build All regressions: FAIL: compilers-m68k-linux-gnu-coldfire gcc build FAIL: compilers-m68k-linux-gnu-coldfire-soft gcc build All failures: FAIL: compilers-m68k-linux-gnu-coldfire gcc build FAIL: compilers-m68k-linux-gnu-coldfire-soft gcc build All changed results: PASS -> UNRESOLVED: compilers-m68k-linux-gnu-coldfire done PASS -> FAIL: compilers-m68k-linux-gnu-coldfire gcc build PASS -> UNRESOLVED: compilers-m68k-linux-gnu-coldfire gcc install PASS -> UNRESOLVED: compilers-m68k-linux-gnu-coldfire-soft done PASS -> FAIL: compilers-m68k-linux-gnu-coldfire-soft gcc build PASS -> UNRESOLVED: compilers-m68k-linux-gnu-coldfire-soft gcc install Component versions for this build: binutils: vcs-mainline (68830fbae98867f63720d250a18ce64f9f2f51fc) gcc: vcs-mainline (f56d48b2471c388401174029324e1f4c4b84fcdb) glibc: vcs-mainline (8775479804cfea2bbe4dcdf19d6589264c96d5fb) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (e45542fbd6cbc0a815b0808f16cf4a8e87410f64) hurd: vcs-mainline (8bc29be6ce900f3e6c683d030fa69ca915fcd969) linux: 6.0 (6.0) mig: vcs-mainline (68b3d8fe3a9595b7a5cb2bb6bc5973ba26139704) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-10-21 10:47 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=166634925295.1234.13050252507144259126@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).