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-04-20 15:17:56 build results Date: Thu, 20 Apr 2023 17:35:36 +0000 [thread overview] Message-ID: <168201213657.2606510.5082211934405135952@build4-jammy-cs.sje.mentorg.com> (raw) All regressions: FAIL: glibcs-i686-gnu check-compilers All failures: FAIL: glibcs-i686-gnu check-compilers All changed results: UNRESOLVED -> PASS: glibcs-microblaze-linux-gnu build UNRESOLVED -> PASS: glibcs-microblaze-linux-gnu check FAIL -> PASS: glibcs-microblaze-linux-gnu check-compilers UNRESOLVED -> PASS: glibcs-microblaze-linux-gnu configure UNRESOLVED -> PASS: glibcs-microblaze-linux-gnu install UNRESOLVED -> PASS: glibcs-microblaze-linux-gnu mkdir UNRESOLVED -> PASS: glibcs-microblaze-linux-gnu mkdir-lib UNRESOLVED -> PASS: glibcs-microblaze-linux-gnu rm UNRESOLVED -> PASS: glibcs-microblazeel-linux-gnu build UNRESOLVED -> PASS: glibcs-microblazeel-linux-gnu check FAIL -> PASS: glibcs-microblazeel-linux-gnu check-compilers UNRESOLVED -> PASS: glibcs-microblazeel-linux-gnu configure UNRESOLVED -> PASS: glibcs-microblazeel-linux-gnu install UNRESOLVED -> PASS: glibcs-microblazeel-linux-gnu mkdir UNRESOLVED -> PASS: glibcs-microblazeel-linux-gnu mkdir-lib UNRESOLVED -> PASS: glibcs-microblazeel-linux-gnu rm Component versions for this build: binutils: vcs-mainline (b6b746e6b81c69588d7ca07708b307bd7728b0ac) gcc: vcs-mainline (0be4fbeaa6a7a2db466a6fd2efad2afdb642bac0) glibc: vcs-mainline (65cbd52174f5bc211dd655727c2239e25e55bfce) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (13e393e8d43c3509956ffee5cf27fc2311b649fd) hurd: vcs-mainline (9f7cfaa5c02ffbf83f909ed6e5cb9467bcc76a49) linux: 6.2 (6.2) mig: vcs-mainline (4c0f2ff0a1432f7e1794cf29b1a4667e3a0f8f89) mpc: 1.3.1 (1.3.1) mpfr: 4.2.0 (4.2.0)
reply other threads:[~2023-04-20 17:35 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=168201213657.2606510.5082211934405135952@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).