From: Mark Wielaard <mark@klomp.org>
To: gcc-rust@gcc.gnu.org
Subject: Re: ☠ Buildbot (GNU Toolchain): gccrust - failed 'grep unexpected ...' (failure) (master)
Date: Wed, 11 May 2022 20:30:08 +0200 [thread overview]
Message-ID: <YnwAsKOoQLrS17lV@wildebeest.org> (raw)
In-Reply-To: <20220511180616.855423856DE7@sourceware.org>
Hi,
On Wed, May 11, 2022 at 06:06:16PM +0000, builder--- via Gcc-rust wrote:
> A new failure has been detected on builder gccrust-debian-ppc64 while building gccrust.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/3/builds/103
>
> Build state: failed 'grep unexpected ...' (failure)
> Revision: 502c8a859750064103bb71f4d559cef7b1c1b8af
> Worker: debian-ppc64
> Build Reason: (unknown)
> Blamelist: David Faust <david.faust@oracle.com>, bors[bot] <26634292+bors[bot]@users.noreply.github.com>
[...]
> A new failure has been detected on builder gccrust-fedora-s390x while building gccrust.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/37/builds/103
>
> Build state: failed 'grep unexpected ...' (failure)
> Revision: 502c8a859750064103bb71f4d559cef7b1c1b8af
> Worker: fedora-s390x
> Build Reason: (unknown)
> Blamelist: David Faust <david.faust@oracle.com>, bors[bot] <26634292+bors[bot]@users.noreply.github.com>
So both of these are:
FAIL: rust/compile/macro-issue1233.rs (test for excess errors)
Executing on host: /home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs-build/gcc/testsuite/rust/../../gccrs -B/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs-build/gcc/testsuite/rust/../../ /home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs -fdiagnostics-plain-output -w -S -o macro-issue1233.s (timeout = 10)
spawn -ignore SIGHUP /home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs-build/gcc/testsuite/rust/../../gccrs -B/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs-build/gcc/testsuite/rust/../../ /home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs -fdiagnostics-plain-output -w -S -o macro-issue1233.s
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:9:21: error: expected [()] got [u8]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:7:44: error: expected [u8] got [()]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:9:21: error: expected [()] got [u16]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:7:44: error: expected [u16] got [()]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:9:21: error: expected [()] got [u32]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:7:44: error: expected [u32] got [()]
compiler exited with status 1
FAIL: rust/compile/macro-issue1233.rs (test for excess errors)
Excess errors:
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:9:21: error: expected [()] got [u8]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:7:44: error: expected [u8] got [()]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:9:21: error: expected [()] got [u16]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:7:44: error: expected [u16] got [()]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:9:21: error: expected [()] got [u32]
/home/mjw/bb/wildebeest/gccrust-fedora-s390x/gccrs/gcc/testsuite/rust/compile/macro-issue1233.rs:7:44: error: expected [u32] got [()]
But it is unclear whether this was introduced by this patch by David:
https://code.wildebeest.org/git/mirror/gccrs/commit/?id=502c8a859750064103bb71f4d559cef7b1c1b8af
typecheck: add is_primitive_type_kind helper
That is because the commits are done somewhat randomly. The log looks
like a Christmas tree:
https://code.wildebeest.org/git/mirror/gccrs/log/
So bors only tests merged batches of commits, possibly on top on some
very old commits. While the buildbot tests each commit individually.
I am not sure what to do about this. As is I think the buildbot isn't
super useful because bors keeps putting these untested commits in the
tree.
Cheers,
Mark
next prev parent reply other threads:[~2022-05-11 18:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 18:06 builder
2022-05-11 18:30 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 11:17 builder
2022-12-07 15:50 builder
2022-12-07 15:47 builder
2022-11-30 10:53 builder
2022-11-07 14:09 builder
2022-10-27 19:59 builder
2022-10-26 16:25 builder
2022-10-21 16:03 builder
2022-09-30 16:21 builder
2022-09-27 7:02 builder
2022-09-27 6:49 builder
2022-08-31 10:44 builder
2022-08-25 16:37 builder
2022-08-22 15:30 builder
2022-08-19 15:07 builder
2022-08-17 12:54 builder
2022-08-09 15:36 builder
2022-08-09 15:33 builder
2022-08-09 14:53 builder
2022-08-05 13:57 builder
2022-08-05 10:37 builder
2022-08-04 20:34 builder
2022-07-22 11:58 builder
2022-07-15 17:46 builder
2022-07-15 19:18 ` Mark Wielaard
2022-07-07 10:34 builder
2022-06-01 9:33 builder
2022-05-26 9:53 builder
2022-05-26 13:15 ` Mark Wielaard
2022-05-19 10:43 builder
2022-05-10 18:05 builder
2022-05-10 11:00 builder
2022-05-10 11:38 ` Mark Wielaard
2022-05-10 12:18 ` dkm
2022-05-09 11:33 builder
2022-04-28 19:48 builder
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=YnwAsKOoQLrS17lV@wildebeest.org \
--to=mark@klomp.org \
--cc=gcc-rust@gcc.gnu.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).