public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Tom de Vries <tdevries@suse.de>
Cc: Jan Beulich <jbeulich@suse.com>, buildbot@sourceware.org
Subject: Re: error: file write error: No space left on device
Date: Mon, 4 Jul 2022 12:23:24 +0200	[thread overview]
Message-ID: <YsK/nGm5BlvWCExP@wildebeest.org> (raw)
In-Reply-To: <a6db64c6-5e3a-59f2-12a8-68843cb230c3@suse.de>

On Mon, Jul 04, 2022 at 10:58:19AM +0200, Tom de Vries wrote:
> [ was: Re: ☠ Buildbot (GNU Toolchain): binutils-gdb - failed update
> (failure) (master) ]
> 
> I see in the logs "error: file write error: No space left on device"

Oops. So many images, so many builds.  I cleaned some space. Will have
to reboot the machines later today to give them more disk space
permanently.

Cheers,

Mark


      reply	other threads:[~2022-07-04 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220704083933.4974A3858C52@sourceware.org>
2022-07-04  8:58 ` Tom de Vries
2022-07-04 10:23   ` Mark Wielaard [this message]

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=YsK/nGm5BlvWCExP@wildebeest.org \
    --to=mark@klomp.org \
    --cc=buildbot@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=tdevries@suse.de \
    /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).