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 10 glibcs 2022-01-06 14:00:13 build results
Date: Thu, 6 Jan 2022 17:15:19 +0000 [thread overview]
Message-ID: <164148931915.27532.6866688264461156377@build6-trusty-cs.sje.mentorg.com> (raw)
All failures:
FAIL: glibcs-or1k-linux-gnu-soft check-compilers
Component versions for this build:
binutils: vcs-2.37 (9bc6649d7b87b73a619ed2769c1bd98cec1bb6a2)
gcc: vcs-10 (0d566335a31722f8044852d9a24f492830ae5789)
glibc: vcs-mainline (65ccd641bacea33be23d51da737c2de7543d0f5e)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (63ed32b135317b7884c3feaa5b5e873aa15b7f07)
hurd: vcs-mainline (ad63bae03cf0eb9edced3803cbcd0cee02377050)
linux: 5.15 (5.15)
mig: vcs-mainline (e9482b80272f673f625ac80d49ffea6b79fb6117)
mpc: 1.2.1 (1.2.1)
mpfr: 4.1.0 (4.1.0)
reply other threads:[~2022-01-06 17:15 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=164148931915.27532.6866688264461156377@build6-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: link
Be 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).