Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: Breakage on builder Fedora-x86_64-cc-with-index, revision 81b42bcab16f4462eb4c91db2cf09cd76e17402e
Date: Wed, 01 Nov 2017 17:08:00 -0000	[thread overview]
Message-ID: <877evaexk1.fsf@redhat.com> (raw)
In-Reply-To: <664f122d-7ec2-7f55-ec7f-da2e61c20dc5@ericsson.com> (Simon	Marchi's message of "Wed, 1 Nov 2017 11:43:27 -0400")

On Wednesday, November 01 2017, Simon Marchi wrote:

> Hi Sergio,

Hey Simon,

> These failures are caused by an x86-64 buildslave being out of disk space.
> I guess it's one of the GCC compile farm machines, but I don't know which
> one.  Could you look into it, or tell which machine fedora-x86-64-1 maps to?

Sorry about that.  This machine actually lives at the Toronto office and
is managed directly by me.  While I was on vacation, its hard disk died,
and I only managed to replace it yesterday.  I installed Fedora on
"automatic mode", and it chose to create a 15GB root partition instead
of use the 1TB disk...  Sigh.  Anyway, I've resized the partition and
things should work OK now.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2017-11-01 17:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 15:37 Oh dear. I regret to inform you that commit 81b42bcab16f4462eb4c91db2cf09cd76e17402e might be unfortunate gdb-buildbot
2017-11-01 15:37 ` Breakage on builder Fedora-x86_64-cc-with-index, revision 81b42bcab16f4462eb4c91db2cf09cd76e17402e gdb-buildbot
2017-11-01 15:44   ` Simon Marchi
2017-11-01 17:08     ` Sergio Durigan Junior [this message]
2017-11-01 17:30       ` Simon Marchi

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=877evaexk1.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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