From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
oe-core <openembedded-core@lists.openembedded.org>
Cc: "LOCK, JOSHUA" <joshua.g.lock@intel.com>
Subject: Re: About runqemu's use cases
Date: Tue, 13 Sep 2016 09:34:55 +0100 [thread overview]
Message-ID: <1473755695.7207.26.camel@linuxfoundation.org> (raw)
In-Reply-To: <7df73b67-6880-ee6c-a18a-1e2a6ac9e5b7@windriver.com>
On Tue, 2016-09-13 at 10:53 +0800, Robert Yang wrote:
> Hello,
>
> We have a new oe-core/scripts/runqemu now, and I'd like to add
> something
> like "runqemu test" in the future to avoid regressions. It would help
> a
> lot if you can provide the info about how do you use runqemu. There
> is
> a bug tracking this:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10249
>
> You can reply here or reply in the bug.
Wouldn't this be a case for "oe-selftest -r runqemu" and create a
runqemu test suite within oe-selftest like we do for other components?
Cheers,
Richard
next prev parent reply other threads:[~2016-09-13 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 2:53 About runqemu's use cases Robert Yang
2016-09-13 8:34 ` Richard Purdie [this message]
2016-09-13 8:39 ` Robert Yang
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=1473755695.7207.26.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=joshua.g.lock@intel.com \
--cc=liezhi.yang@windriver.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