From: Mark Wielaard <mark@klomp.org>
To: gcc-rust@gcc.gnu.org
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
Date: Sun, 13 Jun 2021 01:51:19 +0200 [thread overview]
Message-ID: <YMVIdymavfD7n52N@wildebeest.org> (raw)
In-Reply-To: <20210612233801.89F26949EBD@builder.wildebeest.org>
Hi,
On Sat, Jun 12, 2021 at 11:38:01PM +0000, buildbot@builder.wildebeest.org wrote:
> The Buildbot has detected a new failure on builder gccrust-debian-arm64 while building gccrust.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/58/builds/45
>
> Buildbot URL: https://builder.wildebeest.org/buildbot/
>
> Worker for this Build: debian-arm64
>
> Build Reason: <unknown>
> Blamelist: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
>
> BUILD FAILED: failed compile (failure)
Sorry, that was my fault, I was experimenting with ccache to speed up
builds, but misconfigured things. It should be setup correctly now.
At least we know now that the buildbot sents out emails when something
goes wrong.
Apologies,
Mark
next prev parent reply other threads:[~2021-06-12 23:51 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 23:38 buildbot
2021-06-12 23:51 ` Mark Wielaard [this message]
2021-06-18 11:06 buildbot
2021-06-18 11:31 ` Mark Wielaard
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
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
2021-08-22 15:55 buildbot
2021-08-22 16:22 ` Mark Wielaard
2021-09-25 12:04 buildbot
2021-09-25 13:18 ` Mark Wielaard
2021-11-05 13:49 buildbot
2021-11-05 14:26 ` Mark Wielaard
2021-12-19 17:13 buildbot
2021-12-20 17:10 ` 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
2022-01-29 16:20 buildbot
2022-01-29 20:23 ` Mark Wielaard
2022-02-05 16:58 buildbot
2022-02-05 17:12 ` Mark Wielaard
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-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-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-23 11:48 buildbot
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-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-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-22 12:41 buildbot
2022-03-22 13:08 ` Mark Wielaard
2022-03-22 13:09 ` Arthur Cohen
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=YMVIdymavfD7n52N@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).