From: Mark Wielaard <mark@klomp.org>
To: gcc-rust@gcc.gnu.org
Cc: Arthur Cohen <arthur.cohen@embecosm.com>,
Faisal Abbas <90.abbasfaisal@gmail.com>,
Sebastien Lacoste <dev@graphman.fr>
Subject: Re: ☠ Buildbot (GNU Toolchain): gccrust - failed compile (failure) (master)
Date: Fri, 24 Jun 2022 11:31:32 +0200 [thread overview]
Message-ID: <YrWEdHgPQ8Z+piRK@wildebeest.org> (raw)
In-Reply-To: <20220624092121.C19F4385414E@sourceware.org>
Hi,
On Fri, Jun 24, 2022 at 09:21:21AM +0000, builder--- via Gcc-rust wrote:
> A new failure has been detected on builder gccrust-bootstrap-debian-amd64 while building gccrust.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/107/builds/2
>
> Build state: failed compile (failure)
> Revision: 5d7841fa235cd53a807dae813d20f474362fb5c1
> Worker: bb3
> Build Reason: (unknown)
> Blamelist: Arthur Cohen <arthur.cohen@embecosm.com>, Faisal Abbas <90.abbasfaisal@gmail.com>, Sebastien Lacoste <dev@graphman.fr>, bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Sorry for this and the other failure email. I added a bootstrap
builder for gccrust to builder.sourceware.org but the bootstrap is
currently broken. I posted a fix here:
https://code.wildebeest.org/git/user/mjw/gccrs/commit/?h=packed
https://sourceware.org/pipermail/gcc-rust/2022-June/000355.html
And I also made the mistake of turning all builders into bootstrap
builders... So they all failed. That has been fixed and there is now
just one (failing) bootstrap builder and the other builders do a
non-bootstrap build now (except for s390x those all succeed).
Cheers,
Mark
next prev parent reply other threads:[~2022-06-24 9:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 9:21 builder
2022-06-24 9:31 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-21 15:14 builder
[not found] <20220825153123.2C3763852759@sourceware.org>
2022-08-25 16:40 ` Mark Wielaard
2022-08-25 16:36 builder
2022-08-25 16:36 builder
2022-08-25 15:31 builder
2022-06-27 9:16 builder
2022-06-24 9:15 builder
2022-04-28 11:17 builder
2022-04-28 11:40 ` Mark Wielaard
2022-04-25 20:37 builder
2022-04-22 14:15 builder
2022-04-22 13:29 builder
2022-04-22 13:36 ` Mark Wielaard
2022-04-21 20:19 builder
2022-04-21 18:32 builder
2022-04-21 19:45 ` 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=YrWEdHgPQ8Z+piRK@wildebeest.org \
--to=mark@klomp.org \
--cc=90.abbasfaisal@gmail.com \
--cc=arthur.cohen@embecosm.com \
--cc=dev@graphman.fr \
--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).