From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] randconfig, allyesconfig: fix handling of legacy options
Date: Thu, 8 Jan 2015 21:43:27 +0100 [thread overview]
Message-ID: <20150108214327.415ff023@free-electrons.com> (raw)
In-Reply-To: <54AEEA65.1040501@mind.be>
Dear Arnout Vandecappelle,
On Thu, 08 Jan 2015 21:36:53 +0100, Arnout Vandecappelle wrote:
> >> I admit it's not really an issue introduced by the patch as the issue
> >> already exists for randpackageconfig. But it's very annoying :/
> >
> > Any comment about this?
>
> Well, as you explained to me in Dusseldorf, the main reason to use randconfig
> is to test against buggy Config.in depends/select chains. If the choices
> wouldn't get properly randomized anymore, that would really kill this use case.
> So I guess that's a no go.
Well, the other day, I actually attempted to use randconfig to really
have random configurations, and see how broken they are. But randconfig
is unusable today, since it selects a bunch of legacy options, which
prevents the build from starting.
I'm not sure I actually use randconfig to test buggy Config.in
depends/select. I actually tend to use randpackageconfig: I fix a
certain arch/toolchain combination, and sent to a bit of
randpackageconfig. Which indeed means that I'm not testing everything
since the choices are not randomized.
Do we have a hope of getting properly randomized choices one day. Are
there other options?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-08 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 9:24 [Buildroot] [PATCH v3 1/2] randconfig, allyesconfig: fix handling of legacy options Arnout Vandecappelle
2014-10-14 9:24 ` [Buildroot] [PATCH v3 2/2] randconfig: seed with BR2_RAND_PRESEED_CONFIG_FILES Arnout Vandecappelle
2014-10-19 9:00 ` Yann E. MORIN
2014-10-30 22:03 ` [Buildroot] [PATCH v3 1/2] randconfig, allyesconfig: fix handling of legacy options Thomas Petazzoni
2014-12-31 14:17 ` Thomas Petazzoni
2015-01-08 20:36 ` Arnout Vandecappelle
2015-01-08 20:43 ` Thomas Petazzoni [this message]
2015-01-24 23:00 ` 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=20150108214327.415ff023@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.