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] Autobuilder news
Date: Fri, 29 Aug 2014 23:26:12 +0200	[thread overview]
Message-ID: <20140829232612.0d94e265@free-electrons.com> (raw)

Hello,

Here are a few news about the autobuilders:

 * Two new build machines are being added to the infrastructure, thanks
   to the contributions of Buildroot developers. One is managed by
   Richard Braun and has already been reporting a number of build
   results since a day or two. The other machine is managed by
   Nathaniel Roach and is currently being verified by running local
   builds not yet reported to autobuild.buildroot.org. The builds
   should start to be reported tomorrow. Thanks to Richard's machine,
   the average number of builds per day is now in the order of 130-150
   per day, compared to 100-120 before.

 * Thanks to a patch from Fabio Porcedda, the configuration files
   presented by autobuild.buildroot.org for each build no longer
   contain the BR2_DL_DIR and BR2_JLEVEL options that were specific to
   the build machine. It makes easier the reproduction of a build
   result (as a reminder, there is a script available at
   http://git.buildroot.net/buildroot-test/plain/utils/br-reproduce-build
   to reproduce builds).

 * I've added a quick and dirty script to more easily remove bogus
   builds from the build database
   (http://git.buildroot.net/buildroot-test/tree/utils/remove.php). In
   the past, it was quite annoying for me to remove build results, as I
   had to do manual SQL queries and removal of build result artifacts
   in the filesystem. Now, it's much easier with this script, which
   I've already used to remove the bogus build results generated by
   Nathaniel attempts to use the autobuild-run script.

 * I've added a check on autobuild.buildroot.org to detect and reject
   build failures caused by memory allocation problems. Whenever the
   end of the build log contains "fork: cannot allocate memory", the
   build result is rejected. This should avoid some bogus build
   failures reported by gcc10, which is under heavy load and therefore
   make build fails for a reason not related to Buildroot.

Best regards,

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

             reply	other threads:[~2014-08-29 21:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 21:26 Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-04 20:36 [Buildroot] Autobuilder news Thomas Petazzoni
2014-05-04 21:32 ` Luca Ceresoli
2014-05-10 20:28 ` Arnout Vandecappelle
2014-05-11 16:07   ` Thomas Petazzoni
2014-05-11 16:29   ` Thomas Petazzoni
2014-05-11 20:37     ` Arnout Vandecappelle
2014-05-11 21:14       ` 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=20140829232612.0d94e265@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