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 12 glibcs 2023-02-11 11:08:02 build results Date: Sat, 11 Feb 2023 13:24:57 +0000 [thread overview] Message-ID: <167612189749.1261476.6251110260688500776@build3-jammy-cs.sje.mentorg.com> (raw) New regressions: FAIL: glibcs-s390-linux-gnu check-compilers FAIL: glibcs-s390x-linux-gnu check-compilers FAIL: glibcs-s390x-linux-gnu-O3 check-compilers All regressions: FAIL: glibcs-s390-linux-gnu check-compilers FAIL: glibcs-s390x-linux-gnu check-compilers FAIL: glibcs-s390x-linux-gnu-O3 check-compilers All failures: FAIL: glibcs-s390-linux-gnu check-compilers FAIL: glibcs-s390x-linux-gnu check-compilers FAIL: glibcs-s390x-linux-gnu-O3 check-compilers All changed results: PASS -> UNRESOLVED: glibcs-s390-linux-gnu build PASS -> UNRESOLVED: glibcs-s390-linux-gnu check PASS -> FAIL: glibcs-s390-linux-gnu check-compilers PASS -> UNRESOLVED: glibcs-s390-linux-gnu configure PASS -> UNRESOLVED: glibcs-s390-linux-gnu install PASS -> UNRESOLVED: glibcs-s390-linux-gnu mkdir PASS -> UNRESOLVED: glibcs-s390-linux-gnu mkdir-lib PASS -> UNRESOLVED: glibcs-s390-linux-gnu rm PASS -> UNRESOLVED: glibcs-s390x-linux-gnu build PASS -> UNRESOLVED: glibcs-s390x-linux-gnu check PASS -> FAIL: glibcs-s390x-linux-gnu check-compilers PASS -> UNRESOLVED: glibcs-s390x-linux-gnu configure PASS -> UNRESOLVED: glibcs-s390x-linux-gnu install PASS -> UNRESOLVED: glibcs-s390x-linux-gnu mkdir PASS -> UNRESOLVED: glibcs-s390x-linux-gnu mkdir-lib PASS -> UNRESOLVED: glibcs-s390x-linux-gnu rm FAIL -> UNRESOLVED: glibcs-s390x-linux-gnu-O3 build PASS -> FAIL: glibcs-s390x-linux-gnu-O3 check-compilers PASS -> UNRESOLVED: glibcs-s390x-linux-gnu-O3 configure PASS -> UNRESOLVED: glibcs-s390x-linux-gnu-O3 mkdir PASS -> UNRESOLVED: glibcs-s390x-linux-gnu-O3 rm Component versions for this build: binutils: vcs-2.40 (90fa46db61d98d754d3b5b2726ec3b0ca0588210) gcc: vcs-12 (8f68a9b8e413ecb73d9c407364f778166c28a5d0) glibc: vcs-mainline (e42ec822190056895e55e5140ce2304e67e34445) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (cd86f005ee31fd6e9bfdb378cf3fba22964a6598) hurd: vcs-mainline (56d065041793509a6f60671f6ae3400698bd5639) linux: 6.1 (6.1) mig: vcs-mainline (d76280e4fc71265b88bce2bdaf25b3be846fc6b2) mpc: 1.3.1 (1.3.1) mpfr: 4.2.0 (4.2.0)
reply other threads:[~2023-02-11 13:25 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=167612189749.1261476.6251110260688500776@build3-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).