From: Tom de Vries <tdevries@suse.de>
To: Jan Beulich <jbeulich@suse.com>,
buildbot@sourceware.org, Mark Wielaard <mark@klomp.org>
Subject: error: file write error: No space left on device
Date: Mon, 4 Jul 2022 10:58:19 +0200 [thread overview]
Message-ID: <a6db64c6-5e3a-59f2-12a8-68843cb230c3@suse.de> (raw)
In-Reply-To: <20220704083933.4974A3858C52@sourceware.org>
[ 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"
Thanks,
- Tom
On 7/4/22 10:39, builder@sourceware.org wrote:
> A new failure has been detected on builder gdb-opensusetw-x86_64 while building binutils-gdb.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/97/builds/345
>
> Build state: failed update (failure)
> Revision: (unknown)
> Worker: bb2
> Build Reason: (unknown)
> Blamelist: Jan Beulich <jbeulich@suse.com>, Tom de Vries <tdevries@suse.de>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/97/builds/345/steps/1/logs/stdio
>
> A new failure has been detected on builder gdb-rawhide-x86_64 while building binutils-gdb.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/136/builds/19
>
> Build state: failed update (failure)
> Revision: (unknown)
> Worker: bb2
> Build Reason: (unknown)
> Blamelist: Jan Beulich <jbeulich@suse.com>, Tom de Vries <tdevries@suse.de>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/136/builds/19/steps/1/logs/stdio
>
> A new failure has been detected on builder gdb-debian-testing-x86_64 while building binutils-gdb.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/148/builds/5
>
> Build state: failed compile (failure)
> Revision: 2c474c46943e5242f356a0c0676e2f7bd223c8a9
> Worker: bb2
> Build Reason: (unknown)
> Blamelist: Jan Beulich <jbeulich@suse.com>, Tom de Vries <tdevries@suse.de>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/148/builds/5/steps/1/logs/stdio
>
> - 2: rm -rf gdb-build ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/148/builds/5/steps/2/logs/stdio
>
> - 3: configure ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/148/builds/5/steps/3/logs/stdio
>
> - 4: make ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/148/builds/5/steps/4/logs/stdio
> - warnings (17): https://builder.sourceware.org/buildbot/#builders/148/builds/5/steps/4/logs/warnings__17_
>
next parent reply other threads:[~2022-07-04 8:58 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 [this message]
2022-07-04 10:23 ` 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=a6db64c6-5e3a-59f2-12a8-68843cb230c3@suse.de \
--to=tdevries@suse.de \
--cc=buildbot@sourceware.org \
--cc=jbeulich@suse.com \
--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).