public inbox for
 help / color / mirror / Atom feed
From: Philip Herron <>
To: Mark Wielaard <>
Subject: Re: make check-rust doesn't fail, but now the buildbot does
Date: Wed, 23 Feb 2022 11:57:51 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Thanks for doing this I've been investigating the issue with the 2
match expressions I think it's down to the layout of the enum type not
being correct. Not quite sure what the fix will be yet.

Overall it's just great to have this level of feedback automatically
on multiple machines.


On Tue, 22 Feb 2022 at 23:59, Mark Wielaard <> wrote:
> Hi,
> make check-rust doesn't fail if there are any unexpected failuress.
> I couldn't figure out why not. So I added a new step to the buildbot
> so that it does grep unexpected gcc/testsuite/rust/rust.sum; test $? == 1"
> which should make the build fail if there are any unexpected test results.
> If this works at least the debian-i686 builder should start failing
> because it has a couple of failing test results.
> Cheers,
> Mark
> --
> Gcc-rust mailing list

      reply	other threads:[~2022-02-23 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 23:59 Mark Wielaard
2022-02-23 11:57 ` Philip Herron [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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).