From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <joshua.g.lock@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] image: add mechanism to run QA checks on the image once it's built
Date: Tue, 07 Jun 2016 17:59:36 +0100 [thread overview]
Message-ID: <1465318776.13979.79.camel@linuxfoundation.org> (raw)
In-Reply-To: <1465311037-17658-1-git-send-email-joshua.g.lock@intel.com>
On Tue, 2016-06-07 at 15:50 +0100, Joshua Lock wrote:
> Add a mechanism to run QA checks on a constructed image once it's
> complete. All checks will be run with any one failure resulting in
> a failed build.
How is that different to the testimage class (which tests images after
they're built)?
Cheers,
Richard
next prev parent reply other threads:[~2016-06-07 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 14:50 [PATCH] image: add mechanism to run QA checks on the image once it's built Joshua Lock
2016-06-07 15:48 ` Christopher Larson
2016-06-07 20:48 ` Joshua G Lock
2016-06-07 16:59 ` Richard Purdie [this message]
2016-06-07 20:50 ` Joshua G 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=1465318776.13979.79.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=joshua.g.lock@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