From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/6] oeqa/targetcontrol.py: modify it to test runqemu
Date: Fri, 17 Mar 2017 11:54:19 +0000 [thread overview]
Message-ID: <1489751659.13980.135.camel@linuxfoundation.org> (raw)
In-Reply-To: <751ae73c98c1280f2b5ada3b442cf3f5828ed437.1489657029.git.liezhi.yang@windriver.com>
On Thu, 2017-03-16 at 03:13 -0700, Robert Yang wrote:
> Modify the following files to test runqemu:
> targetcontrol.py
> utils/commands.py
> utils/qemurunner.py
>
> We need simulate how "runqemu" works in command line, so when test
> "runqemu", the targetcontrol.py, utils/commands.py and
> utils/qemurunner.py don't have to find the rootfs or set env vars.
>
> [YOCTO #10249]
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> meta/lib/oeqa/targetcontrol.py | 20 +++++++++++++++-----
> meta/lib/oeqa/utils/commands.py | 13 +++++++++++--
> meta/lib/oeqa/utils/qemurunner.py | 28 +++++++++++++++++-----------
> 3 files changed, 43 insertions(+), 18 deletions(-)
This change breaks "oe-selftest -r wic.Wic.test_qemu_efi" which just
hangs afterwards.
Cheers,
Richard
next prev parent reply other threads:[~2017-03-17 11:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 10:13 [PATCH 0/6] runqemu: add selftest and fixes Robert Yang
2017-03-16 10:13 ` [PATCH 1/6] runqemu: improve when no machine specified Robert Yang
2017-03-16 10:13 ` [PATCH 2/6] runqemu: add -h and --help Robert Yang
2017-03-16 10:13 ` [PATCH 3/6] runqemu: only boot ramfs when specified Robert Yang
2017-03-16 10:13 ` [PATCH 4/6] oeqa/targetcontrol.py: modify it to test runqemu Robert Yang
2017-03-17 11:54 ` Richard Purdie [this message]
2017-03-20 9:45 ` Robert Yang
2017-03-16 10:13 ` [PATCH 5/6] selftest/runqemu.py: add " Robert Yang
2017-03-16 10:13 ` [PATCH 6/6] targetcontrol.py: use logger.info to replace of bb.note 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=1489751659.13980.135.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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