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 2023-01-28 10:28:11 build results Date: Sat, 28 Jan 2023 12:33:12 +0000 [thread overview] Message-ID: <167490919212.1850398.8538681668946474619@build4-jammy-cs.sje.mentorg.com> (raw) All regressions: FAIL: compilers-ia64-linux-gnu glibc ia64-linux-gnu build 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-ia64-linux-gnu glibc ia64-linux-gnu build 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-i686-gnu done UNRESOLVED -> PASS: compilers-i686-gnu gcc build UNRESOLVED -> PASS: compilers-i686-gnu gcc configure UNRESOLVED -> PASS: compilers-i686-gnu gcc install UNRESOLVED -> PASS: compilers-i686-gnu gcc mkdir UNRESOLVED -> PASS: compilers-i686-gnu gcc rm FAIL -> PASS: compilers-i686-gnu glibc i686-gnu build UNRESOLVED -> PASS: compilers-i686-gnu glibc i686-gnu install UNRESOLVED -> PASS: compilers-i686-gnu glibc i686-gnu mkdir-lib Component versions for this build: binutils: vcs-mainline (ccc42eb23136d314fc97315b2443b14f952db15c) gcc: vcs-mainline (4c1f9ff82582a62a1c10514dcdf7bc7456e5ca19) glibc: vcs-mainline (90dffec958f4d423435d155939ef8abf4fedd1f1) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (a8fbf3737be9a6f5fd1d87765072292d54e54aac) hurd: vcs-mainline (bf721cfb73ffcf887d4e33a9338789bd56281f79) linux: 6.1 (6.1) mig: vcs-mainline (a9db7bcc04530e19223b5037bb8420fa4344b183) mpc: 1.3.1 (1.3.1) mpfr: 4.2.0 (4.2.0)
reply other threads:[~2023-01-28 12:33 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=167490919212.1850398.8538681668946474619@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).