From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Some topics for the Buildroot Developer Day
Date: Tue, 25 Oct 2011 08:02:19 +0200 [thread overview]
Message-ID: <87vcrdy5g4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4EA5C53B.5000406@eukrea.com> ("Eric Bénard"'s message of "Mon, 24 Oct 2011 22:06:19 +0200")
>>>>> "Eric" == Eric B?nard <eric@eukrea.com> writes:
Eric> Hi Thomas,
Eric> Le 24/10/2011 21:47, Thomas Petazzoni a ?crit :
>> Ok. However note that for the moment, we're only trying to do automated
>> *build* testing. Automated *runtime* testing is an entirely different
>> story.
>>
Eric> you may be interested in buildbot or jenkins :
Eric> http://trac.buildbot.net/
Eric> http://jenkins-ci.org/
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.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-10-25 6:02 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 [this message]
2011-10-25 6:34 ` Robert Schwebel
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=87vcrdy5g4.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.