From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot autobuilders - Cleanup faulty tarballs
Date: Tue, 16 Dec 2014 08:02:56 +0100 [thread overview]
Message-ID: <20141216080256.09901ee4@free-electrons.com> (raw)
In-Reply-To: <20141215230340.GB4075@free.fr>
Dear Yann E. MORIN,
On Tue, 16 Dec 2014 00:03:40 +0100, Yann E. MORIN wrote:
> Could you please remove the tarballs from SF-hosted packages on each
> autobuilder instance you are running, please? You'll find that list
> below.
Done. Note that I did not simply remove the Sourceforge tarballs, but
simply completely removed the download directories of each autobuild
instance I was managing. This has two consequences:
* A few invalid failures being reported, such as
http://autobuild.buildroot.org/results/8da/8daafed00348b4498c7dfe2b34e060338b2f10eb/build-end.log.
There should be no more than the number of instances I was taking of
(4 on the Free Electrons build server, 4 on the gcc75 machine).
* Probably a higher number of reports about failed downloads, since
wiping out the download directory means that the next builds will
re-download everything they need, which gives a higher probability
of downloading tarballs that have disappeared, or trying to reach
hosts that are down, etc.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-16 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 23:03 [Buildroot] Buildroot autobuilders - Cleanup faulty tarballs Yann E. MORIN
2014-12-16 7:02 ` Thomas Petazzoni [this message]
2014-12-16 17:31 ` Yann E. MORIN
2014-12-16 20:02 ` Thomas Petazzoni
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=20141216080256.09901ee4@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.