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 glibcs 2023-01-24 23:42:47 build results Date: Wed, 25 Jan 2023 01:56:23 +0000 [thread overview] Message-ID: <167461178322.2027387.7477079745916847289@build4-jammy-cs.sje.mentorg.com> (raw) All regressions: FAIL: glibcs-ia64-linux-gnu check-compilers FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers All failures: FAIL: glibcs-ia64-linux-gnu check-compilers FAIL: glibcs-m68k-linux-gnu-coldfire check-compilers FAIL: glibcs-m68k-linux-gnu-coldfire-soft check-compilers All changed results: UNRESOLVED -> PASS: glibcs-csky-linux-gnuabiv2 build UNRESOLVED -> PASS: glibcs-csky-linux-gnuabiv2 check FAIL -> PASS: glibcs-csky-linux-gnuabiv2 check-compilers UNRESOLVED -> PASS: glibcs-csky-linux-gnuabiv2 configure UNRESOLVED -> PASS: glibcs-csky-linux-gnuabiv2 install UNRESOLVED -> PASS: glibcs-csky-linux-gnuabiv2 mkdir UNRESOLVED -> PASS: glibcs-csky-linux-gnuabiv2 mkdir-lib UNRESOLVED -> PASS: glibcs-csky-linux-gnuabiv2 rm Component versions for this build: binutils: vcs-mainline (b1a41f59270a4efd57e354e46ab735eb163c66ca) gcc: vcs-mainline (1c407dc088231ba5f2cc63d9278f4b797db48de1) glibc: vcs-mainline (33f0f58b59751a0cb0dd1611175d0211f567bede) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (7d6e296b4256c8c1002f053a9aeefc077a0363b3) hurd: vcs-mainline (bf721cfb73ffcf887d4e33a9338789bd56281f79) linux: 6.1 (6.1) mig: vcs-mainline (a9db7bcc04530e19223b5037bb8420fa4344b183) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2023-01-25 1:56 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=167461178322.2027387.7477079745916847289@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).