From: Mark Wielaard <mark@klomp.org>
To: Luis Machado <luis.machado@arm.com>
Cc: buildbot@sourceware.org, binutils@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed update (failure) (master)
Date: Fri, 22 Jul 2022 11:58:13 +0200 [thread overview]
Message-ID: <Ytp0tSIvlxJEMs+O@wildebeest.org> (raw)
In-Reply-To: <56af4b2b-e87c-6fd0-e5c1-93f834947bdd@arm.com>
Hi Luis,
On Fri, Jul 22, 2022 at 01:52:30AM +0100, Luis Machado wrote:
> On 7/21/22 20:41, builder--- via Binutils wrote:
> > A new failure has been detected on builder binutils-debian-ppc64 while building binutils-gdb.
> >
> > Full details are available at:
> > https://builder.sourceware.org/buildbot/#builders/78/builds/373
> >
> > Build state: failed update (failure)
> > Revision: (unknown)
> > Worker: debian-ppc64
> > Build Reason: (unknown)
> > Blamelist: Andrew Burgess <aburgess@redhat.com>, H.J. Lu <hjl.tools@gmail.com>, Tom de Vries <tdevries@suse.de>, Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
> >
> > Steps:
> >
> > - 0: worker_preparation ( success )
> >
> > - 1: git checkout ( failure )
> > Logs:
> > - stdio: https://builder.sourceware.org/buildbot/#builders/78/builds/373/steps/1/logs/stdio
> >
>
> It seems the builder ran out of disk space.
Yes it did (and the ppc64le worker too). We keep all builds, which can
add up. So now we do a make clean at the end to save some space:
https://sourceware.org/pipermail/buildbot/2022q3/000162.html
Both workers have 5GB to 10GB free again now.
Sorry for the trouble.
Cheers,
Mark
next parent reply other threads:[~2022-07-22 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220721194111.2AE56383A37A@sourceware.org>
[not found] ` <56af4b2b-e87c-6fd0-e5c1-93f834947bdd@arm.com>
2022-07-22 9:58 ` Mark Wielaard [this message]
[not found] <20220816074708.104EA3858418@sourceware.org>
[not found] ` <de9b1e96-3e5f-fbc5-dd64-6254ffc80273@suse.com>
2022-08-17 11:30 ` 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=Ytp0tSIvlxJEMs+O@wildebeest.org \
--to=mark@klomp.org \
--cc=binutils@sourceware.org \
--cc=buildbot@sourceware.org \
--cc=luis.machado@arm.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).