From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] runqemu/testimage logging fixes
Date: Mon, 9 Dec 2019 23:59:04 +1300 [thread overview]
Message-ID: <cover.1575888923.git.paul.eggleton@linux.intel.com> (raw)
A fix for https://bugzilla.yoctoproject.org/show_bug.cgi?id=13681 along
with some fixes for other minor related issues with the logging when
testimage runs QEMU.
(The "host dump" functionality may be of questionable usefulness, but
at least it now works again.)
The following changes since commit d821415ab09248a894d58f6e5a5749e822d30939:
wayland: Add PACKAGECONFIG for dtd-validation (2019-12-09 10:21:24 +0000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/runqemu-fixes-oe
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/runqemu-fixes-oe
Paul Eggleton (5):
oeqa: qemu: ensure that host dump commands can be run properly
oeqa: qemu: fix width of top output in host dump
oeqa: qemu: ensure we print runqemu output in the event of failure
runqemu: log parameters correctly within testimage
runqemu: handle tap device creation failure properly
meta/lib/oeqa/utils/dump.py | 5 ++++-
meta/lib/oeqa/utils/qemurunner.py | 4 ++--
scripts/runqemu | 33 ++++++++++++++++++-------------
3 files changed, 25 insertions(+), 17 deletions(-)
--
2.20.1
next reply other threads:[~2019-12-09 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 10:59 Paul Eggleton [this message]
2019-12-09 10:59 ` [PATCH 1/5] oeqa: qemu: ensure that host dump commands can be run properly Paul Eggleton
2019-12-09 10:59 ` [PATCH 2/5] oeqa: qemu: fix width of top output in host dump Paul Eggleton
2019-12-09 10:59 ` [PATCH 3/5] oeqa: qemu: ensure we print runqemu output in the event of failure Paul Eggleton
2019-12-09 10:59 ` [PATCH 4/5] runqemu: log parameters correctly within testimage Paul Eggleton
2019-12-09 10:59 ` [PATCH 5/5] runqemu: handle tap device creation failure properly Paul Eggleton
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=cover.1575888923.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.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