From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Nick Clifton <nickc@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Breakage on builder Fedora-s390x-m64, revision beab453223769279cc1cef68a1622ab8978641f7
Date: Fri, 30 Nov 2018 21:06:00 -0000 [thread overview]
Message-ID: <87efb2qnqg.fsf@redhat.com> (raw)
In-Reply-To: <20181130205754.GM31795@wildebeest.org> (Mark Wielaard's message of "Fri, 30 Nov 2018 21:57:54 +0100")
On Friday, November 30 2018, Mark Wielaard wrote:
> On Fri, Nov 30, 2018 at 01:10:00PM -0500, Sergio Durigan Junior wrote:
>> > *** Internal error on buildslave (no space left on device). ***
>> > *** Please report this to the buildslave owner (see <http://gdb-build.sergiodj.net//buildslaves/marist-fedora-s390x>) ***
>> >
>> > *** Failed to compiled GDB. ***
>>
>> Nick, sorry about this false-positive. It is a problem with the builder
>> machine running out of space.
>>
>> Hey Mark, can you please take a look at this?
>
> I cleaned up some disk space. But there is still only 1GB of free space
> left. I'll contact the server admin to see if we can get some more space.
Thanks, man. Much appreciated!
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2018-11-30 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 11:51 Oh dear. I regret to inform you that commit beab453223769279cc1cef68a1622ab8978641f7 might be unfortunate gdb-buildbot
2018-11-30 11:51 ` Breakage on builder Fedora-s390x-m64, revision beab453223769279cc1cef68a1622ab8978641f7 gdb-buildbot
2018-11-30 18:10 ` Sergio Durigan Junior
2018-11-30 20:58 ` Mark Wielaard
2018-11-30 21:06 ` Sergio Durigan Junior [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=87efb2qnqg.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=nickc@redhat.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