[Buildroot] [autobuild.buildroot.net] Build results for 2013-10-24

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Dear Gustavo Zacarias,

On Mon, 28 Oct 2013 08:12:12 -0300, Gustavo Zacarias wrote:

> Hetzner reached back and their opinion is that they're firewall rules
> (because ping+trace work and http doesn't).
> I don't know their networking setup but it sounds reasonable (some odd
> balancer setup might show these symptoms).
> I guess the server admin is a bit aggresive on recurrent fetchers.
> Which moves me to the question, shouldn't the autobuilders just build?
> Checking the sources is great but it shouldn't be so aggresive on
> upstream servers, small projects might not be so happy about it.
> I know this has to be coded but maybe it's time.

Originally, the autobuilders had a cache on a per build thread basis
(my build server runs 3 builds in parallel). So it meant that a given
tarball what at the maximum downloaded three times.

However, since some time, I have changed this to remove 5 random
tarballs after each build, so that the cache gets progressively
refreshed, and the autobuilders also check upstream URLs. I've done
that after we had realized that several of our upstream URLs in
Buildroot were broken, which directly affects new users (but wasn't
visible in the autobuilders).

I can certainly adjust the policy by reducing the number of removed
tarballs to 1 or 2 after each build, for example. But I still believe
that doing this allows us to verify the upstream URLs thanks to the
autobuilders.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com