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 2022-09-07 14:02:15 build results Date: Wed, 7 Sep 2022 19:34:58 +0000 [thread overview] Message-ID: <166257929814.32659.414155011684199839@build9-trusty-cs.sje.mentorg.com> (raw) All regressions: FAIL: compilers-m68k-linux-gnu-coldfire-soft glibc m68k-linux-gnu-coldfire-soft build All failures: FAIL: compilers-m68k-linux-gnu-coldfire-soft glibc m68k-linux-gnu-coldfire-soft build All changed results: UNRESOLVED -> PASS: compilers-powerpc64-linux-gnu done UNRESOLVED -> PASS: compilers-powerpc64-linux-gnu gcc build UNRESOLVED -> PASS: compilers-powerpc64-linux-gnu gcc configure UNRESOLVED -> PASS: compilers-powerpc64-linux-gnu gcc install UNRESOLVED -> PASS: compilers-powerpc64-linux-gnu gcc mkdir UNRESOLVED -> PASS: compilers-powerpc64-linux-gnu gcc rm FAIL -> PASS: compilers-powerpc64-linux-gnu glibc powerpc64-linux-gnu build UNRESOLVED -> PASS: compilers-powerpc64-linux-gnu glibc powerpc64-linux-gnu install UNRESOLVED -> PASS: compilers-powerpc64-linux-gnu glibc powerpc64-linux-gnu mkdir-lib UNRESOLVED -> PASS: compilers-powerpc64le-linux-gnu done UNRESOLVED -> PASS: compilers-powerpc64le-linux-gnu gcc build UNRESOLVED -> PASS: compilers-powerpc64le-linux-gnu gcc configure UNRESOLVED -> PASS: compilers-powerpc64le-linux-gnu gcc install UNRESOLVED -> PASS: compilers-powerpc64le-linux-gnu gcc mkdir UNRESOLVED -> PASS: compilers-powerpc64le-linux-gnu gcc rm FAIL -> PASS: compilers-powerpc64le-linux-gnu glibc powerpc64le-linux-gnu build UNRESOLVED -> PASS: compilers-powerpc64le-linux-gnu glibc powerpc64le-linux-gnu install UNRESOLVED -> PASS: compilers-powerpc64le-linux-gnu glibc powerpc64le-linux-gnu mkdir-lib Component versions for this build: binutils: vcs-mainline (154f2735ad4c2eb0985086b113825e6f4f3abcf1) gcc: vcs-mainline (0a91bdaf177409a2a5e7895bce4f0e7091b4b3ca) glibc: vcs-mainline (89d40cacd0aed35e2546513ce01924b879523e46) gmp: 6.2.1 (6.2.1) gnumach: vcs-mainline (66775cd2279be8e81269c06575c836900aa64793) hurd: vcs-mainline (da8d2ba4b61a7d6b25f5b2215447795f2b9badf9) linux: 5.19 (5.19) mig: vcs-mainline (68b3d8fe3a9595b7a5cb2bb6bc5973ba26139704) mpc: 1.2.1 (1.2.1) mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-09-07 19: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=166257929814.32659.414155011684199839@build9-trusty-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).