From: Philip Herron <philip.herron@embecosm.com>
To: Mark Wielaard <mark@klomp.org>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: ☝ Buildbot (GNU Toolchain): gccrust - worker cancelled (master)
Date: Tue, 24 May 2022 10:29:34 +0100 [thread overview]
Message-ID: <CAB2u+n0wzviBhbmtXLj__jJ1KetQEQTOfuLZweTnSnk-LVokLQ@mail.gmail.com> (raw)
In-Reply-To: <Yow1QAngqWShkFWS@wildebeest.org>
Hi Mark,
A full bootstrap once a day might be nice to have actually. I wonder
how long it will take on this build bot.
Hopefully, the bots don't unionize and go on strike for being overworked :).
--Phil
On Tue, 24 May 2022 at 02:30, Mark Wielaard <mark@klomp.org> wrote:
>
> Hi,
>
> On Tue, May 24, 2022 at 01:01:55AM +0000, builder--- via Gcc-rust wrote:
> > A cancelled build has been detected on builder gccrust-fedora-x86_64 while building gccrust.
> >
> > Full details are available at:
> > https://builder.sourceware.org/buildbot/#builders/16/builds/131
> >
> > Build state: worker cancelled
> > Revision: (unknown)
> > Worker: bb2
> > Build Reason: (unknown)
> > Blamelist: Philip Herron <philip.herron@embecosm.com>
> >
> > Steps:
> >
> > - 0: worker_preparation ( cancelled )
>
> Apologies, that was me playing with the new container image builder.
> It all works now. And the now builder seems fast enough to maybe do a
> full bootstrap build (once a day?)
>
> Cheers,
>
> Mark
>
> --
> Gcc-rust mailing list
> Gcc-rust@gcc.gnu.org
> https://gcc.gnu.org/mailman/listinfo/gcc-rust
next prev parent reply other threads:[~2022-05-24 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 1:01 builder
2022-05-24 1:30 ` Mark Wielaard
2022-05-24 9:29 ` Philip Herron [this message]
2022-06-19 0:32 ` gccrust debian stable bootstrap builder (Was: ☝ Buildbot (GNU Toolchain): gccrust - worker cancelled (master)) Mark Wielaard
2022-08-25 16:36 ☝ Buildbot (GNU Toolchain): gccrust - worker cancelled (master) 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=CAB2u+n0wzviBhbmtXLj__jJ1KetQEQTOfuLZweTnSnk-LVokLQ@mail.gmail.com \
--to=philip.herron@embecosm.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=mark@klomp.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).