* [Buildroot] gc20 no space left issue
@ 2016-10-09 18:45 Thomas Petazzoni
2016-10-09 19:20 ` Peter Korsgaard
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Petazzoni @ 2016-10-09 18:45 UTC (permalink / raw)
To: buildroot
Hello Peter,
Due to a lack of disk space, gcc20 reports some build failures, such as:
http://autobuild.buildroot.net/results/6a2/6a2d4cb453128c0aa1fc9ed0ac04ec7c8306e7e1/
Could you see if you can fix this ?
Perhaps we should start thinking about a way of ignoring the build
results caused by a lack of disk space ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] gc20 no space left issue
2016-10-09 18:45 [Buildroot] gc20 no space left issue Thomas Petazzoni
@ 2016-10-09 19:20 ` Peter Korsgaard
2016-10-09 19:53 ` Thomas Petazzoni
0 siblings, 1 reply; 3+ messages in thread
From: Peter Korsgaard @ 2016-10-09 19:20 UTC (permalink / raw)
To: buildroot
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello Peter,
> Due to a lack of disk space, gcc20 reports some build failures, such as:
> http://autobuild.buildroot.net/results/6a2/6a2d4cb453128c0aa1fc9ed0ac04ec7c8306e7e1/
> Could you see if you can fix this ?
I dropped some of the bigger tarballs from instance-*/dl, so now there's
11G free.
> Perhaps we should start thinking about a way of ignoring the build
> results caused by a lack of disk space ?
Perhaps, if we can come up with a simple & robust way of detecting
it. On the other hand, this doesn't happen that often - And when it does
it is good to get notified about it.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] gc20 no space left issue
2016-10-09 19:20 ` Peter Korsgaard
@ 2016-10-09 19:53 ` Thomas Petazzoni
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Petazzoni @ 2016-10-09 19:53 UTC (permalink / raw)
To: buildroot
Hello,
On Sun, 09 Oct 2016 21:20:13 +0200, Peter Korsgaard wrote:
> > Could you see if you can fix this ?
>
> I dropped some of the bigger tarballs from instance-*/dl, so now there's
> 11G free.
OK.
> > Perhaps we should start thinking about a way of ignoring the build
> > results caused by a lack of disk space ?
>
> Perhaps, if we can come up with a simple & robust way of detecting
> it. On the other hand, this doesn't happen that often - And when it does
> it is good to get notified about it.
Yes, I don't know if we can detect it reliably, indeed. Let's keep
things as they are for now.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-10-09 19:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-10-09 18:45 [Buildroot] gc20 no space left issue Thomas Petazzoni
2016-10-09 19:20 ` Peter Korsgaard
2016-10-09 19:53 ` Thomas Petazzoni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox