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] Changes in the Buildroot autobuilders
Date: Sun, 16 Jun 2013 18:00:54 +0200	[thread overview]
Message-ID: <20130616180054.58f52914@skate> (raw)

Hello,

I've made a number of small changes in the autobuilders configuration
and setup:

 *) I've extended the mail notification script to be able to send
    per-architecture notification to persons who are specifically taking
    care of a given architecture. So far, Sonic Zhang is receiving a
    notification for Blackfin related failures, and Mischa Jonker is
    receiving a notification for ARC related failures.

 *) On the Free Electrons build server, I've modified the build script
    so that before every build, it removes 5 random files from the
    download directory. This will allow to make sure the autobuilders
    sometimes re-download tarballs or git trees, and therefore we
    should notice sooner when something is no longer available. For
    example, I've discovered that both the axel and the Blackfin
    toolchain downloads were broken, but that wasn't noticeable due to
    the tarballs already being in the download cache of the
    autobuilders.

 *) I've updated the toolchain configurations on the Free Electrons
    build server. All external toolchains built by Buildroot have been
    rebuilt using Buildroot 2013.05 (tarballs available at
    http://autobuild.buildroot.org/toolchains/tarballs/). Many
    configurations that used external toolchains have been updated to
    use the latest available versions of those toolchains and I've added
    a MIPS64 configuration that uses the Sourcery toolchain. See
    http://autobuild.buildroot.org/toolchains/configs/free-electrons/
    for the complete list of toolchains.

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-06-16 16:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 16:00 Thomas Petazzoni [this message]
2013-06-16 17:03 ` [Buildroot] Changes in the Buildroot autobuilders Yann E. MORIN
2013-06-16 17:18   ` Thomas Petazzoni
2013-06-16 17:25     ` Yann E. MORIN
2013-06-16 18:05       ` Thomas Petazzoni
2013-06-17  7:45         ` Maxime Ripard
2013-06-17  7:49           ` Thomas Petazzoni
2013-06-17 16:20             ` Spenser Gilliland
2013-06-17 17:54               ` Yann E. MORIN
2013-06-17 18:07                 ` ANDY KENNEDY
2013-06-17 20:09                   ` Mischa Jonker
2013-06-18  7:12                     ` Thomas Petazzoni
2013-06-17 20:39                 ` Spenser Gilliland
2013-06-18  6:21                 ` Arnout Vandecappelle
2013-06-18  7:16                   ` Thomas Petazzoni
2013-06-18 16:46                     ` Yann E. MORIN
2013-06-17  6:25       ` Arnout Vandecappelle

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=20130616180054.58f52914@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