From: Xiao Guang Chen <chenxg@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, mimu@linux.vnet.ibm.com,
mreitz@redhat.com
Subject: [Qemu-devel] [PATCH RFC v4 0/6] Update tests/qemu-iotests failing cases for the s390 platform
Date: Thu, 5 Feb 2015 11:44:26 +0800 [thread overview]
Message-ID: <1423107872-3268-1-git-send-email-chenxg@linux.vnet.ibm.com> (raw)
v4:
1. Generate all patches based on the latest master branch.
2. Rearrange patches
v3:
1. Fix a typo in v2.
v2:
1. Drop the patches for test 039 for it has been fixed in upstream.
2. Integrate patches for test 071, 067 and 087.
3. Keep the other patches.
v1:
1. updated the test suite to be default-machine-type-aware, from the previous platform-aware
2. created a new patch "qemu-iotests: run qemu with -nodefaults" to counterpart the impact from the commit:
c88930a6866e74953e931ae749781e98e486e5c8
qemu-char: Permit only a single "stdio" character device
When more than one is used, the terminal settings aren't restored
correctly on exit. Fixable. However, such usage makes no sense,
because the users race for input, so outlaw it instead.
If you want to connect multiple things to stdio, use the mux
chardev.
3. updated all the checking of platform name to the current machine name
Mao Chuan Li (3):
qemu-iotests: qemu machine type support
qemu-iotests: s390x: fix test 041
qemu-iotests: s390x: fix test 051
Xiao Guang Chen (3):
qemu-iotests: run qemu with -nodefaults
qemu-iotests: fix tests 067, 071 and 087
qemu-iotests: s390x: fix test 055
tests/qemu-iotests/041 | 6 +
tests/qemu-iotests/051 | 91 +++++---
tests/qemu-iotests/051.s390-virtio.out | 377 +++++++++++++++++++++++++++++++++
tests/qemu-iotests/055 | 9 +
tests/qemu-iotests/067 | 8 +-
tests/qemu-iotests/067.out | 266 +----------------------
tests/qemu-iotests/071.out | 4 -
tests/qemu-iotests/087.out | 12 --
tests/qemu-iotests/check | 5 +
tests/qemu-iotests/common | 1 +
tests/qemu-iotests/common.config | 3 +-
tests/qemu-iotests/common.qemu | 2 +-
tests/qemu-iotests/iotests.py | 1 +
13 files changed, 469 insertions(+), 316 deletions(-)
create mode 100644 tests/qemu-iotests/051.s390-virtio.out
--
1.9.1
next reply other threads:[~2015-02-05 3:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 3:44 Xiao Guang Chen [this message]
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 1/6] qemu-iotests: run qemu with -nodefaults Xiao Guang Chen
2015-02-05 3:52 ` Fam Zheng
2015-02-05 5:52 ` chen xiao guang
2015-02-05 14:22 ` Max Reitz
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 2/6] qemu-iotests: qemu machine type support Xiao Guang Chen
2015-02-05 14:18 ` Max Reitz
2015-02-05 17:57 ` Eric Blake
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 3/6] qemu-iotests: fix tests 067, 071 and 087 Xiao Guang Chen
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 4/6] qemu-iotests: s390x: fix test 041 Xiao Guang Chen
2015-02-05 14:26 ` Max Reitz
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 5/6] qemu-iotests: s390x: fix test 051 Xiao Guang Chen
2015-02-05 15:11 ` Max Reitz
2015-02-09 8:06 ` chen xiao guang
2015-02-09 14:35 ` Max Reitz
2015-02-05 3:44 ` [Qemu-devel] [PATCH RFC v4 6/6] qemu-iotests: s390x: fix test 055 Xiao Guang Chen
2015-02-05 15:16 ` Max Reitz
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=1423107872-3268-1-git-send-email-chenxg@linux.vnet.ibm.com \
--to=chenxg@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).