From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Add test infrastructure
Date: Tue, 6 Mar 2012 08:06:03 +0100 [thread overview]
Message-ID: <201203060806.03919.arnout@mind.be> (raw)
In-Reply-To: <20120305145625.GE21255@game.jcrosoft.org>
On Monday 05 March 2012 15:56:25 Jean-Christophe PLAGNIOL-VILLARD wrote:
> I like the idea of test but what is the target here?
Good point, I should have explained that.
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.
Another part of this evolution will be to set up a webpage where test
results can be posted and retrieved. Peter was going to do that (but
hasn't had the time yet).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-03-06 7:06 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 [this message]
2012-03-06 8: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=201203060806.03919.arnout@mind.be \
--to=arnout@mind.be \
--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