From: Mark Wielaard <mark@klomp.org>
To: "cohenarthur.dev" <cohenarthur.dev@gmail.com>
Cc: Philip Herron <philip.herron@embecosm.com>, gcc-rust@gcc.gnu.org
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
Date: Sat, 7 Aug 2021 01:19:22 +0200 [thread overview]
Message-ID: <YQ3DeslY9BOb1BvS@wildebeest.org> (raw)
In-Reply-To: <20210806155509.f4advlfv4zvdrr6k@oneshade>
Hi Arthur,
On Fri, Aug 06, 2021 at 05:55:09PM +0200, cohenarthur.dev via Gcc-rust wrote:
> I'm really sorry about not having all the commits build. I tried to keep
> them as atomic as possible and clearly didn't check all of them
> separately. This could have been a single commit and would have avoided
> this, but since each change was big I decided to split them up.
>
> I was not aware that buildbot checks every commit separately. I think
> this is a good feature, and I'll keep it in mind. Won't happen again!
No worries, that is what the bots are for. We are all human, but the
bots aren't :)
It would be more helpful if the buildbot workers ran a bit earlier.
Cheers,
Mark
next prev parent reply other threads:[~2021-08-06 23:19 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 15:15 buildbot
2021-08-04 20:25 ` Mark Wielaard
2021-08-06 14:31 ` Philip Herron
2021-08-06 15:55 ` cohenarthur.dev
2021-08-06 23:19 ` Mark Wielaard [this message]
2021-08-08 11:52 ` Philip Herron
2021-08-06 22:39 ` Mark Wielaard
2021-08-08 11:51 ` Philip Herron
2021-08-08 12:09 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2022-03-22 12:41 buildbot
2022-03-22 13:08 ` Mark Wielaard
2022-03-22 13:09 ` Arthur Cohen
2022-03-07 9:49 buildbot
2022-03-07 9:57 ` Arthur Cohen
2022-03-07 14:23 ` Mark Wielaard
2022-03-07 14:32 ` Arthur Cohen
2022-03-07 14:42 ` Mark Wielaard
2022-03-08 14:32 ` Arthur Cohen
2022-03-06 22:01 buildbot
2022-03-06 22:20 ` Mark Wielaard
2022-03-06 22:33 ` Mark Wielaard
2022-03-07 8:54 ` Arthur Cohen
2022-03-01 19:08 buildbot
2022-03-01 23:15 ` Mark Wielaard
2022-03-02 7:21 ` Thomas Schwinge
2022-03-02 9:03 ` Philip Herron
2022-03-02 9:44 ` Thomas Schwinge
2022-03-02 10:05 ` Thomas Schwinge
2022-03-02 12:05 ` Arthur Cohen
2022-03-02 12:36 ` Thomas Schwinge
2022-03-02 13:31 ` Arthur Cohen
2022-03-02 10:00 ` Mark Wielaard
2022-02-23 11:48 buildbot
2022-02-23 10:26 buildbot
2022-02-23 10:35 ` Mark Wielaard
2022-02-23 11:26 ` Mark Wielaard
2022-02-23 23:19 ` Mark Wielaard
2022-02-18 12:11 buildbot
2022-02-18 12:48 ` dkm
2022-02-18 13:30 ` Mark Wielaard
2022-02-18 15:20 ` Thomas Fitzsimmons
2022-02-17 19:26 buildbot
2022-02-17 19:46 ` Marc
2022-02-17 21:05 ` Mark Wielaard
2022-02-17 22:03 ` Mark Wielaard
2022-02-05 16:58 buildbot
2022-02-05 17:12 ` Mark Wielaard
2022-01-29 16:20 buildbot
2022-01-29 20:23 ` Mark Wielaard
2022-01-24 12:29 buildbot
2022-01-24 12:37 ` Mark Wielaard
2022-01-24 21:30 ` Marc
2022-01-25 7:33 ` Thomas Schwinge
2022-01-25 22:42 ` Mark Wielaard
2022-01-29 20:20 ` Mark Wielaard
2022-02-03 20:55 ` Thomas Schwinge
2022-02-04 10:23 ` Mark Wielaard
2021-12-19 17:13 buildbot
2021-12-20 17:10 ` Mark Wielaard
2021-11-05 13:49 buildbot
2021-11-05 14:26 ` Mark Wielaard
2021-09-25 12:04 buildbot
2021-09-25 13:18 ` Mark Wielaard
2021-08-22 15:55 buildbot
2021-08-22 16:22 ` Mark Wielaard
2021-06-18 11:06 buildbot
2021-06-18 11:31 ` Mark Wielaard
2021-06-12 23:38 buildbot
2021-06-12 23:51 ` 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=YQ3DeslY9BOb1BvS@wildebeest.org \
--to=mark@klomp.org \
--cc=cohenarthur.dev@gmail.com \
--cc=gcc-rust@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).