* error: file write error: No space left on device [not found] <20220704083933.4974A3858C52@sourceware.org> @ 2022-07-04 8:58 ` Tom de Vries 2022-07-04 10:23 ` Mark Wielaard 0 siblings, 1 reply; 2+ messages in thread From: Tom de Vries @ 2022-07-04 8:58 UTC (permalink / raw) To: Jan Beulich, buildbot, Mark Wielaard [ 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_ > ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: error: file write error: No space left on device 2022-07-04 8:58 ` error: file write error: No space left on device Tom de Vries @ 2022-07-04 10:23 ` Mark Wielaard 0 siblings, 0 replies; 2+ messages in thread From: Mark Wielaard @ 2022-07-04 10:23 UTC (permalink / raw) To: Tom de Vries; +Cc: Jan Beulich, buildbot 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-07-04 10:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20220704083933.4974A3858C52@sourceware.org>
2022-07-04 8:58 ` error: file write error: No space left on device Tom de Vries
2022-07-04 10:23 ` Mark Wielaard
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).