From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2014-04-19
Date: Wed, 23 Apr 2014 11:05:55 +0200 [thread overview]
Message-ID: <20140423110555.60b6da2d@skate> (raw)
In-Reply-To: <435816036.13835416.1398243362765.JavaMail.root@openwide.fr>
Dear Jeremy Rosen,
On Wed, 23 Apr 2014 10:56:02 +0200 (CEST), Jeremy Rosen wrote:
> on a side note, if the autobuilder has selected a high number of packages
> so far, there are probably many "low number of packages" type of bug
> that it could find. it might be interesting to temporarly set it to a
> low number of packages...
As I said, the randomization is randomized. The percentage used for
KCONFIG_PROBABILITY is itself randomized between 1% and 30%. So some
builds will have 1% of BR2_PACKAGE_<foo> options enabled, some will
have 30% of options defined.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-23 9:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-19 Thomas Petazzoni
2014-04-20 8:48 ` [Buildroot] Analysis of build " Thomas Petazzoni
2014-04-20 13:09 ` Mike Zick
2014-04-21 17:35 ` Luca Ceresoli
2014-04-22 20:25 ` [Buildroot] php / snmp / iconv problem Thomas Petazzoni
2014-04-23 1:17 ` Gustavo Zacarias
2014-04-22 16:41 ` [Buildroot] Analysis of build results for 2014-04-19 Arnout Vandecappelle
2014-04-22 20:19 ` Thomas Petazzoni
2014-04-22 22:14 ` Arnout Vandecappelle
2014-04-23 7:22 ` Thomas Petazzoni
2014-04-23 8:51 ` Arnout Vandecappelle
2014-04-23 8:56 ` Jeremy Rosen
2014-04-23 9:02 ` Arnout Vandecappelle
2014-04-23 9:05 ` Thomas Petazzoni [this message]
2014-04-23 8:59 ` 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=20140423110555.60b6da2d@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 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.