Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-08-07
Date: Thu, 8 Aug 2013 20:46:31 +0200	[thread overview]
Message-ID: <20130808204631.1a482566@skate> (raw)
In-Reply-To: <CAAXf6LVewPXENrKj_-ib2iNAFFk-4+sV=EPKxzZbMCP79TXKjg@mail.gmail.com>

Dear Thomas De Schampheleire,

On Thu, 8 Aug 2013 13:55:17 +0200, Thomas De Schampheleire wrote:
> On Thu, Aug 8, 2013 at 8:30 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> >      i686 |           host-libglib2-2.36.3 | NOK | http://autobuild.buildroot.net/results/4ef2adf5ba85a84ba6ff2ae77d2913ba09897b8d/
> 
> "No space left on device"
> 
> Does this happen regularly? Is space that tight?

No, it doesn't happen that often. There is plenty of space on this
machine. The particular machine on which this build took place (gcc110)
has plenty of disk space:

/dev/md1         539G   14G  497G   3% /
/dev/md0         788M  156M  592M  21% /boot
/dev/md3         2,0G  207M  1,7G  12% /tmp
/dev/md4         1,6T  1,1T  466G  70% /home

But I believe that at the time of the build failure, something was
consuming a lot of disk space. These machines are shared, and it relies
on the good behavior of all users to work properly. So sometimes, a
mail is sent on the users mailing list to ask people to do some clean
up.

So I think we can simply discard those results and concentrate on the
real ones :-)

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-08-08 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-08-07 Thomas Petazzoni
2013-08-08 11:55 ` Thomas De Schampheleire
2013-08-08 18:46   ` Thomas Petazzoni [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=20130808204631.1a482566@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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