From: Robert Schwebel <r.schwebel@pengutronix.de>
To: buildroot@busybox.net
Subject: [Buildroot] Some topics for the Buildroot Developer Day
Date: Tue, 25 Oct 2011 08:34:44 +0200 [thread overview]
Message-ID: <20111025063444.GI9199@pengutronix.de> (raw)
In-Reply-To: <87vcrdy5g4.fsf@macbook.be.48ers.dk>
On Tue, Oct 25, 2011 at 08:02:19AM +0200, Peter Korsgaard wrote:
> Yes, I'm using buildbot at work for the defconfigs we use, and it
> works very well - But the problem is how to get good test coverage of
> our 700+ package / toolchain / kernel combinations?
>
> What I'm currently doing is simply lots of 'make randpackageconfig'
> builds - But it generates lots of data, so I haven't found a good way
> of putting this information online.
When we started with tests, we quickly found out that you don't only
have to be able to test, but also have to cope with what you'll find :)
So if you find lots of broken things, you have to fix them, and that
quickly becomes a lot of work.
So our current strategy is to have a set of "real-life" configs
(customer BSPs), plus corner cases (a config with all-yes). We build
that for the most important platforms (x86/powerpc/arm) and on the
kernels which have most relevance for us (linus-git, linux-next) on a
nightly base. That doesn't cover everything, but seems to be a good
compromise.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-10-25 6:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 15:38 [Buildroot] Some topics for the Buildroot Developer Day Thomas Petazzoni
2011-10-24 16:59 ` Robert Schwebel
2011-10-24 19:47 ` Thomas Petazzoni
2011-10-24 20:06 ` Eric Bénard
2011-10-25 6:02 ` Peter Korsgaard
2011-10-25 6:34 ` Robert Schwebel [this message]
2011-10-25 7:15 ` Peter Korsgaard
2011-10-25 12:20 ` Robert Schwebel
2011-10-24 21:44 ` Shawn J. Goff
2011-10-25 5:53 ` Mike Frysinger
2011-10-24 22:54 ` Quotient Remainder
2011-10-25 6:24 ` Thomas Petazzoni
2011-10-25 7:13 ` Peter Korsgaard
2011-10-25 8:26 ` Thomas De Schampheleire
2011-10-26 12:48 ` Yegor Yefremov
2011-10-26 13:05 ` Gustavo Zacarias
2011-10-29 6:20 ` Thomas Petazzoni
2011-10-29 11:36 ` Gustavo Zacarias
2011-11-18 16:48 ` Thomas Petazzoni
2011-10-30 20:29 ` 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=20111025063444.GI9199@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--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