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-08-02 21:29:51 build results
Date: Wed, 3 Aug 2022 02:59:22 +0000	[thread overview]
Message-ID: <165949556288.12128.4190154012985945841@build9-trusty-cs.sje.mentorg.com> (raw)

All changed results:

UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d done
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc build
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc configure
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc install
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc mkdir
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc rm
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc-first build
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc-first configure
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc-first install
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc-first mkdir
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d gcc-first rm
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d build
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d configure
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d install
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d mkdir
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d mkdir-lib
UNRESOLVED -> PASS: compilers-loongarch64-linux-gnu-lp64d glibc loongarch64-linux-gnu-lp64d rm
FAIL -> PASS: compilers-loongarch64-linux-gnu-lp64d linux install-headers

Component versions for this build:

binutils: vcs-mainline (2ba2f096185c201607cdb1571e51e00e8b66e449)
gcc: vcs-mainline (502605a277d36cee1b0570982a16d97a43eace67)
glibc: vcs-mainline (fccadcdf5bed7ee67a6cef4714e0b477d6c8472c)
gmp: 6.2.1 (6.2.1)
gnumach: vcs-mainline (d179d9f1f6249b89acc66223c9cff33b2f1b5e4e)
hurd: vcs-mainline (88ee4ae44bd64e869bca79d0a6c6e6d4577b7170)
linux: 5.19 (5.19)
mig: vcs-mainline (983b56e9f7ef1fdfcf82ad82cc70f939318e599f)
mpc: 1.2.1 (1.2.1)
mpfr: 4.1.0 (4.1.0)


                 reply	other threads:[~2022-08-03  2:59 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=165949556288.12128.4190154012985945841@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: 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).