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 2015-07-08
Date: Thu, 9 Jul 2015 11:29:58 +0200	[thread overview]
Message-ID: <20150709112958.43329535@free-electrons.com> (raw)
In-Reply-To: <87lheplrzc.fsf@dell.be.48ers.dk>

Peter, All,

On Thu, 09 Jul 2015 09:17:43 +0200, Peter Korsgaard wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> 
>  > Build statistics for 2015-07-08
>  > ===============================
> 
>  >         success : 2  
>  >        failures : 1  
>  >        timeouts : 0  
>  >           TOTAL : 3  
> 
> Huh, what happened?

Amongst the new toolchain configurations listed in the toolchain CSV
file, there was one typo: the toolchain config URL was invalid. Due to
this, the Python script has aborted on all autobuilder slaves.

I've fixed the typo now
(http://git.buildroot.net/buildroot-test/commit/?id=00e2fb0d241eb2e2f0e9bac35f24d729b2c0d8a2),
and restarted the autobuilder slaves on the Free Electrons build
machine and on gcc75.

Could you please restart your autobuilders? Also same for Richard.

Sorry for the mess :-/ The autobuild-run script should maybe be a bit
more robust against such kind of problems. Patches welcome!

Best regards,

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

  reply	other threads:[~2015-07-09  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-08 Thomas Petazzoni
2015-07-09  7:17 ` Peter Korsgaard
2015-07-09  9:29   ` Thomas Petazzoni [this message]
2015-07-09  9:48     ` Peter Korsgaard

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=20150709112958.43329535@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox