public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: builder@sourceware.org, binutils@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed update (failure) (master)
Date: Fri, 22 Jul 2022 01:52:30 +0100	[thread overview]
Message-ID: <56af4b2b-e87c-6fd0-e5c1-93f834947bdd@arm.com> (raw)
In-Reply-To: <20220721194111.2AE56383A37A@sourceware.org>

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.

  reply	other threads:[~2022-07-22  0:52 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 19:41 builder
2022-07-22  0:52 ` Luis Machado [this message]
2022-07-22  9:58   ` Mark Wielaard
  -- strict thread matches above, loose matches on Subject: below --
2022-12-17  0:34 builder
2022-10-06  4:31 builder
2022-10-06  0:25 builder
2022-10-05  4:52 builder
2022-10-05  0:19 builder
2022-10-04 13:34 builder
2022-10-03 11:59 builder
2022-09-30  1:34 builder
2022-09-26  6:04 builder
2022-09-26  5:43 builder
2022-09-26  0:38 builder
2022-09-24  0:20 builder
2022-09-22 17:43 builder
2022-09-22 17:20 builder
2022-09-22  7:24 builder
2022-09-20 11:08 builder
2022-09-14  1:55 builder
2022-09-13 13:51 builder
2022-09-08  9:15 builder
2022-09-06 15:19 builder
2022-09-06  0:21 builder
2022-09-05  0:19 builder
2022-09-02 17:15 builder
2022-09-02  6:31 builder
2022-08-30 13:04 builder
2022-08-27  5:16 builder
2022-08-25  9:17 builder
2022-08-24  6:41 builder
2022-08-23  5:29 builder
2022-08-22  2:51 builder
2022-08-20  0:19 builder
2022-08-16  7:47 builder
2022-08-16  0:19 builder
2022-08-15 15:19 builder
2022-08-13  9:02 builder
2022-08-11  5:38 builder
2022-08-05 11:37 builder
2022-08-01  1:41 builder
2022-07-19 14:38 builder
2022-07-16  0:23 builder
2022-07-04 10:43 builder
2022-06-29 11:35 builder
2022-06-28  1:23 builder
2022-06-27  0:18 builder
2022-06-24  0:21 builder
2022-06-02  9:24 builder
2022-05-19 10:58 builder
2022-05-19 11:11 ` 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=56af4b2b-e87c-6fd0-e5c1-93f834947bdd@arm.com \
    --to=luis.machado@arm.com \
    --cc=binutils@sourceware.org \
    --cc=builder@sourceware.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).