From: Mark Wielaard <mark@klomp.org>
To: buildbot@builder.wildebeest.org
Cc: libabigail@sourceware.org
Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset
Date: Wed, 27 Oct 2021 13:14:13 +0200 [thread overview]
Message-ID: <YXk0hblmovrTNOku@wildebeest.org> (raw)
In-Reply-To: <20211027111158.C79BD93135B@builder.wildebeest.org>
Hi,
On Wed, Oct 27, 2021 at 11:11:58AM +0000, buildbot@builder.wildebeest.org wrote:
> The Buildbot has detected a new failure on builder libabigail-fedora-s390x while building libabigail.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/9/builds/737
>
> Buildbot URL: https://builder.wildebeest.org/buildbot/
>
> Worker for this Build: fedora-s390x
Apologies, the worker had ran out of diskspace.
I cleaned up and reran the build, which succeeded:
https://builder.wildebeest.org/buildbot/#/builders/9/builds/738
Cheers,
Mark
next prev parent reply other threads:[~2021-10-27 11:14 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 11:11 buildbot
2021-10-27 11:14 ` Mark Wielaard [this message]
2021-10-27 12:04 ` Dodji Seketeli
-- strict thread matches above, loose matches on Subject: below --
2022-01-17 13:19 buildbot
2021-12-21 19:18 buildbot
2021-12-14 15:55 buildbot
2021-12-15 13:01 ` Mark Wielaard
2021-11-29 8:05 buildbot
2021-11-29 11:23 ` Mark Wielaard
2021-10-18 10:58 buildbot
2021-09-23 12:12 buildbot
2021-09-23 12:19 ` Mark Wielaard
2021-08-11 17:08 buildbot
2021-07-16 10:11 buildbot
2021-07-16 10:33 ` Mark Wielaard
2021-04-12 15:48 buildbot
2021-03-18 16:05 buildbot
2021-03-19 23:03 ` Mark Wielaard
2020-12-02 15:32 buildbot
2020-11-27 16:59 buildbot
2020-11-25 12:52 buildbot
2020-11-25 8:51 buildbot
2020-11-12 10:50 buildbot
2020-11-02 17:21 buildbot
2020-10-27 9:47 buildbot
2020-10-27 11:30 ` Mark Wielaard
2020-10-27 13:12 ` Mark Wielaard
2020-10-28 9:30 ` Dodji Seketeli
2020-10-28 10:12 ` Mark Wielaard
2020-10-14 10:31 buildbot
2020-10-09 9:35 buildbot
2020-07-30 15:29 buildbot
2020-07-30 15:38 ` Mark Wielaard
2020-07-28 14:40 buildbot
2020-07-28 14:41 ` Mark Wielaard
2020-05-04 9:36 buildbot
2020-04-23 13:09 buildbot
2020-04-23 13:32 ` Mark Wielaard
2020-03-26 15:47 buildbot
2020-03-19 10:55 buildbot
2020-03-19 12:25 ` Mark Wielaard
2020-03-20 22:23 ` Dodji Seketeli
2020-03-12 13:41 buildbot
2020-01-01 0:00 buildbot
2020-01-01 0:00 ` Mark Wielaard
2020-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Matthias Maennich via libabigail
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Matthias Maennich via libabigail
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Dodji Seketeli
2019-01-01 0:00 buildbot
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 buildbot
2019-01-01 0:00 buildbot
2018-01-01 0:00 buildbot
2018-01-01 0:00 ` 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=YXk0hblmovrTNOku@wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@builder.wildebeest.org \
--cc=libabigail@sourceware.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).