From: Mark Wielaard <mark@klomp.org>
To: Philip Herron <philip.herron@embecosm.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
gcc-rust@gcc.gnu.org
Subject: Re: Test results for gccrs on Debian unstable aarch64
Date: Thu, 3 Jun 2021 21:05:22 +0200 [thread overview]
Message-ID: <YLkn8oJ7+Dw2m4nW@wildebeest.org> (raw)
In-Reply-To: <CAB2u+n0mEv8=yqra7WbwS9JFfUpYnxfrgQHN=ZHWcwLCvX5Ymg@mail.gmail.com>
On Thu, Jun 03, 2021 at 12:58:46PM +0100, Philip Herron wrote:
> I just had a thought it would be nice if we could keep a matrix of
> different platforms gccrs has been tested on, and they could have states of:
>
> 1. Build Failure
> 2. Test Failures link to log
> 3. Tests pass, no unexpected results
Note that the buildbot could provide that (for the arches it supports).
If you look at:
https://builder.wildebeest.org/buildbot/#/builders?tags=gccrust
you can see which arches are green.
And for each build it publishes the rust.sum and rust.log files
(under the make check link)
Currently I have only enabled the arches that I know are fully green
(x86_64, arm64 and ppc64le). I should add ppc64[be] because that
should also be fully green. I am not sure about enabling enabling
others (arm32, i386 and s390x). It seems a bit pointless to run builds
we know are currently broken.
Cheers,
Mark
next prev parent reply other threads:[~2021-06-03 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 11:28 John Paul Adrian Glaubitz
2021-06-03 11:58 ` Philip Herron
2021-06-03 12:05 ` John Paul Adrian Glaubitz
2021-06-03 12:10 ` Philip Herron
2021-06-03 19:05 ` Mark Wielaard [this message]
2021-06-03 22:16 ` Mark Wielaard
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=YLkn8oJ7+Dw2m4nW@wildebeest.org \
--to=mark@klomp.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=philip.herron@embecosm.com \
/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).