Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V4 00/11] runqemu: refactor it and remove machine knowledge
Date: Tue, 23 Aug 2016 10:05:06 +0100	[thread overview]
Message-ID: <1471943106.16712.101.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1471850849.git.liezhi.yang@windriver.com>

On Mon, 2016-08-22 at 00:52 -0700, Robert Yang wrote:
> * V4
>   - Now the conf files can use @TAP@, @ROOTFS@ and @PORT@ when set
> vars
>     for runqemu, so all the arch info are gone. And also update
> comments
>     in qemuboot.bbclass.
>   - Add var QB_SLIRP_OPT for slirp mode as Nathan suggested, also add
>     QB_TAP_OPT whichi is for tap mode.
>   - Print "Try 'runqemu help' on how to use it" when failed to parse
> args
>     as Nathan suggested.
>   - Fix device locking problems.
>   - Fix nativesdk-qemu-helper.
>   - Fix comments for qemurunner.py/qemutinyrunner.py

This is looking much better, thanks but we've still had some issues:

https://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/870/steps/Running%20Sanity%20Tests/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/856/steps/Running%20Sanity%20Tests/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/870/steps/Running%20Sanity%20Tests/logs/stdio

and:

https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/652/steps/Running%20oe-selftest/logs/stdio

I'm also not sure what caused these, whether it was this patchset or
not:

https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/927/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/901/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/914/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/914/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio
https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/935

Cheers,

Richard




  parent reply	other threads:[~2016-08-23  9:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22  7:52 [PATCH V4 00/11] runqemu: refactor it and remove machine knowledge Robert Yang
2016-08-22  7:52 ` [PATCH V4 01/11] qemuboot.bbclass: add it for runqemu Robert Yang
2016-08-22  7:52 ` [PATCH V4 02/11] qemuarm.conf: set vars " Robert Yang
2016-08-22  7:52 ` [PATCH V4 03/11] qemuarm64.conf: " Robert Yang
2016-08-22  7:52 ` [PATCH V4 04/11] qemux86.conf/qemux86-64.conf: " Robert Yang
2016-08-22  7:52 ` [PATCH V4 05/11] qemumips/qemumips64.conf: " Robert Yang
2016-08-22  7:52 ` [PATCH V4 06/11] qemuppc.conf: " Robert Yang
2016-08-22  7:52 ` [PATCH V4 07/11] qemu.inc: inherit qemuboot.bbclass Robert Yang
2016-08-22  7:52 ` [PATCH V4 08/11] runqemu: refactor it and remove machine knowledge Robert Yang
2016-08-22  7:52 ` [PATCH V4 09/11] python-3.5-manifest.inc: the signal module RDEPENDS on enum Robert Yang
2016-08-22  7:52 ` [PATCH V4 10/11] nativesdk-qemu-helper: fix for new runqemu Robert Yang
2016-08-22  7:52 ` [PATCH V4 11/11] qemurunner.py/qemutinyrunner.py: remove runqemu-internal Robert Yang
2016-08-22 19:44 ` [PATCH V4 00/11] runqemu: refactor it and remove machine knowledge Aníbal Limón
2016-08-23  0:27   ` Robert Yang
2016-08-23  9:05 ` Richard Purdie [this message]
2016-08-23  9:21   ` Robert Yang
2016-08-25 14:36     ` Robert Yang
2016-08-25 21:52       ` Richard Purdie
2016-08-26  6:28         ` 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=1471943106.16712.101.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