public inbox for libc-testresults@sourceware.org help / color / mirror / Atom feed
From: Joseph Myers <josmyers@redhat.com> To: libc-testresults@sourceware.org Subject: GCC mainline glibcs 2024-01-11 00:55:07 build results Date: Thu, 11 Jan 2024 05:12:49 -0000 [thread overview] Message-ID: <170494996920.1404407.8260042246478244184@tor.usersys.redhat.com> (raw) New regressions: FAIL: glibcs-x86_64-gnu check-compilers All regressions: FAIL: glibcs-hppa-linux-gnu check-compilers FAIL: glibcs-x86_64-gnu check-compilers All failures: FAIL: glibcs-hppa-linux-gnu check-compilers FAIL: glibcs-x86_64-gnu check-compilers All changed results: UNRESOLVED -> (Test removed): glibcs-ia64-linux-gnu build UNRESOLVED -> (Test removed): glibcs-ia64-linux-gnu check FAIL -> (Test removed): glibcs-ia64-linux-gnu check-compilers PASS -> (Test removed): glibcs-ia64-linux-gnu cleanup UNRESOLVED -> (Test removed): glibcs-ia64-linux-gnu configure UNRESOLVED -> (Test removed): glibcs-ia64-linux-gnu install UNRESOLVED -> (Test removed): glibcs-ia64-linux-gnu mkdir UNRESOLVED -> (Test removed): glibcs-ia64-linux-gnu mkdir-lib UNRESOLVED -> (Test removed): glibcs-ia64-linux-gnu rm PASS -> (Test removed): glibcs-ia64-linux-gnu save-logs PASS -> UNRESOLVED: glibcs-x86_64-gnu build PASS -> UNRESOLVED: glibcs-x86_64-gnu check PASS -> FAIL: glibcs-x86_64-gnu check-compilers PASS -> UNRESOLVED: glibcs-x86_64-gnu configure PASS -> UNRESOLVED: glibcs-x86_64-gnu install PASS -> UNRESOLVED: glibcs-x86_64-gnu mkdir PASS -> UNRESOLVED: glibcs-x86_64-gnu mkdir-lib PASS -> UNRESOLVED: glibcs-x86_64-gnu rm Component versions for this build: binutils: vcs-mainline (c49f224f9e7df421ad85753532a988ed6f4e87c7) gcc: vcs-mainline (52e809d5cf345ce01fc81be716a57f5b6d5b4545) glibc: vcs-mainline (874214db624a8e6c5d2dbe47419fab126f330d68) gmp: 6.3.0 (6.3.0) gnumach: vcs-mainline (7538b56278a95d87b9a4ddec01e5679376cc5b13) hurd: vcs-mainline (69905110f5d840dbb0e0986f7eade8cfc9d3dafc) linux: 6.6 (6.6) mig: vcs-mainline (e5c3fa44fb75b23dc7100202e52f3d4366447851) mpc: 1.3.1 (1.3.1) mpfr: 4.2.1 (4.2.1)
reply other threads:[~2024-01-11 5:12 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=170494996920.1404407.8260042246478244184@tor.usersys.redhat.com \ --to=josmyers@redhat.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).