From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Where is atom-pc.conf hiding?
Date: Tue, 14 Jun 2011 13:05:18 +0100 [thread overview]
Message-ID: <1308053118.15712.321.camel@rex> (raw)
In-Reply-To: <1308037467.6879.31.camel@lenovo.internal.reciva.com>
On Tue, 2011-06-14 at 08:44 +0100, Phil Blundell wrote:
> On Mon, 2011-06-13 at 15:10 -0700, Tom Rini wrote:
> > Until then, and even afterwards can we please get some testing of
> > non-poky builds done? I know the autobuilder is full but can't we toss
> > a few things onto a personal box and try that a few times a week?
>
> I can probably find some spare cpu cycles to do testing. Is there an
> existing autobuild/autotest infrastructure that we can conveniently use
> to drive the tests and report the status?
Buildbot is what Yocto is using and the documentation/sample config for
what we do is available at:
http://git.yoctoproject.org/cgit.cgi/poky-autobuilder/
Cheers,
Richard
next prev parent reply other threads:[~2011-06-14 12:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 18:31 Where is atom-pc.conf hiding? Koen Kooi
2011-06-13 20:28 ` Saul Wold
2011-06-13 20:36 ` Koen Kooi
2011-06-13 21:30 ` Richard Purdie
2011-06-13 22:10 ` Tom Rini
2011-06-13 22:19 ` Otavio Salvador
2011-06-13 22:35 ` Richard Purdie
2011-06-13 22:44 ` Tom Rini
2011-06-13 23:04 ` Richard Purdie
2011-06-13 23:17 ` Otavio Salvador
2011-06-14 0:02 ` Richard Purdie
2011-06-14 0:09 ` Otavio Salvador
2011-06-14 0:24 ` Paul Eggleton
2011-06-14 7:44 ` Phil Blundell
2011-06-14 12:05 ` Richard Purdie [this message]
2011-06-14 7:40 ` Koen Kooi
2011-06-14 20:20 ` Tom Zanussi
2011-06-14 21:08 ` Koen Kooi
2011-06-14 21:33 ` Tom Zanussi
2011-06-13 20:29 ` Joshua Lock
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=1308053118.15712.321.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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.