From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Add test infrastructure
Date: Tue, 6 Mar 2012 09:29:09 +0100 [thread overview]
Message-ID: <20120306092909.18f8c30c@skate> (raw)
In-Reply-To: <201203060806.03919.arnout@mind.be>
Le Tue, 6 Mar 2012 08:06:03 +0100,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> Currently, ThomasP and Peter are both independently running tests on
> the buildroot tree. We would like to have more testing done. I
> myself have a server available that can do continuous testing.
> However, a single buildbot isn't going to cut it, because it takes
> quite long to build a single configuration. Therefore, I would like
> to put test infrastructure in the buildroot repository so others can
> easily set up their own buildbot.
I am repeating myself here, but anyway. Buildbot is nice if you always
rebuild the same configuration over and over again, to verify that
there are no regressions.
However, the tests that we do with Peter are *random* configuration
builds. And this doesn't really fit within the Buildbot model: you
can't compare the result of a build (success/failure) to another,
because each build uses a different configuration.
Buildbot works fine if you test the defconfigs that we have, or some
other well-known configurations, but I don't really see how it would
apply to randpackageconfig builds, and this is exactly what Peter and I
are doing.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-03-06 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 23:45 [Buildroot] Test infrastructure Arnout Vandecappelle
2012-03-03 23:45 ` [Buildroot] [PATCH 1/2] Add target to print buildroot version Arnout Vandecappelle
2012-03-03 23:45 ` [Buildroot] [PATCH 2/2] Add test infrastructure Arnout Vandecappelle
2012-03-04 0:13 ` Yann E. MORIN
2012-03-04 13:01 ` Arnout Vandecappelle
2012-03-05 14:56 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-06 7:06 ` Arnout Vandecappelle
2012-03-06 8:29 ` Thomas Petazzoni [this message]
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=20120306092909.18f8c30c@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