From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Musat, George L" <george.l.musat@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] oeqa/selftest: New auto bitbake test for poky tiny.
Date: Tue, 24 Mar 2015 09:34:57 +0000 [thread overview]
Message-ID: <1427189697.14020.24.camel@linuxfoundation.org> (raw)
In-Reply-To: <042E875E1B5D414CA9BB78B7D4FA691C2650EF29@IRSMSX107.ger.corp.intel.com>
On Mon, 2015-03-23 at 11:54 +0000, Musat, George L wrote:
> I am viewing this as a build test for the poky-tiny image, that checks
> if the build was fine by booting it and checking that it booted fine
> and checking that it’s indeed a tiny, rather than a runtime test.
Ross does have a point, our other images automatically run their
testimage tests after each rootfs is constructed as part of the normal
build. Why wouldn't we do this for the tiny images too?
Cheers,
Richard
prev parent reply other threads:[~2015-03-24 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 9:24 [PATCH] oeqa/selftest: New auto bitbake test for poky tiny Lucian Musat
2015-03-23 10:38 ` Burton, Ross
2015-03-23 11:54 ` Musat, George L
2015-03-24 9:34 ` Richard Purdie [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=1427189697.14020.24.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=george.l.musat@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox