public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Philip Herron <philip.herron@embecosm.com>
Cc: Thomas Fitzsimmons <fitzsim@fitzsim.org>, gcc@gcc.gnu.org
Subject: Re: GCC Rust git branch
Date: Mon, 31 May 2021 00:49:37 +0200	[thread overview]
Message-ID: <YLQWga/gIPtY11tl@wildebeest.org> (raw)
In-Reply-To: <0f00f1f4-aadd-20ac-f140-8cba7ed73a25@embecosm.com>

Hi,

On Fri, May 28, 2021 at 11:18:20AM +0100, Philip Herron wrote:
> On 28/05/2021 04:05, Thomas Fitzsimmons wrote:
> > I tried building GCC Rust on ppc64le.  With the attached patches,
> > "make check-rust" succeeds with:
> >
> > 		=== rust Summary ===
> >
> > # of expected passes		2368
> > # of expected failures		26
> >
> 
> Thank you so much for doing this, we will merge these later today. The
> results look the same as the numbers were getting on x86 too.

And I am getting the same results on arm64.  To make sure things keep
zero fail I added a fedora-x86_64 and debian_arm64 worker to my
buildbot setup:
https://builder.wildebeest.org/buildbot/#/builders?tags=gccrust
(The red builds were setup bugs, the last build is all green)

I'll try to also add the ppc64le builder. Are there any other arches
that are zero fail?

Once we have a mailinglist I can set it up so that any failures will
sent email to the rust@gcc mailinglist.

It is currently tracking the master branch. Maybe we can integrate it
with the bors setup you have running. But I didn't really understand
where it is running and how it is configured so that it can be
integrated with the buildbot workers.

Note that the workers aren't very fast. Especially the arm64 one. I
takes ~30 minutes for a fully make && make check. So please no more
than 48 patches a day please :)

Cheers,

Mark


  parent reply	other threads:[~2021-05-30 22:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 13:24 Philip Herron
2021-05-24 16:24 ` Joseph Myers
2022-06-08 12:36   ` Thomas Schwinge
2021-05-24 18:29 ` Mark Wielaard
2021-05-28 10:31   ` Philip Herron
2021-05-30 22:33     ` Mark Wielaard
2021-05-28  3:05 ` Thomas Fitzsimmons
2021-05-28 10:18   ` Philip Herron
2021-05-28 11:48     ` Marc Poulhiès
2021-05-30 22:49     ` Mark Wielaard [this message]
2021-05-28  3:22 ` Jason Merrill
2021-05-28 10:19   ` Philip Herron
2022-06-08 10:58     ` Document <gcc-rust@gcc.gnu.org> mailing list (was: GCC Rust git branch) Thomas Schwinge

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=YLQWga/gIPtY11tl@wildebeest.org \
    --to=mark@klomp.org \
    --cc=fitzsim@fitzsim.org \
    --cc=gcc@gcc.gnu.org \
    --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).