qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bo Tu <tubo@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, armbru@redhat.com,
	mimu@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH RFC v9 3/7] qemu-iotests: s390x: fix test 041
Date: Fri, 22 May 2015 09:26:17 +0800	[thread overview]
Message-ID: <1432257981-10411-4-git-send-email-tubo@linux.vnet.ibm.com> (raw)
In-Reply-To: <1432257981-10411-1-git-send-email-tubo@linux.vnet.ibm.com>

From: Xiao Guang Chen <chenxg@linux.vnet.ibm.com>

There is no 'ide-cd' device defined on s390 platform, so
test_medium_not_found() test should be skipped.

Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Michael Mueller <mimu@linux.vnet.ibm.com>
Signed-off-by: Xiao Guang Chen <chenxg@linux.vnet.ibm.com>
---
 tests/qemu-iotests/041 | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/tests/qemu-iotests/041 b/tests/qemu-iotests/041
index 59a8f73..c6abe3c 100755
--- a/tests/qemu-iotests/041
+++ b/tests/qemu-iotests/041
@@ -197,6 +197,9 @@ class TestSingleDrive(ImageMirroringTestCase):
                         'target image does not match source after mirroring')
 
     def test_medium_not_found(self):
+        if iotests.qemu_default_machine != 'pc':
+            return
+
         result = self.vm.qmp('drive-mirror', device='ide1-cd0', sync='full',
                              target=target_img)
         self.assert_qmp(result, 'error/class', 'GenericError')
@@ -867,6 +870,9 @@ class TestRepairQuorum(ImageMirroringTestCase):
         if not self.has_quorum():
             return
 
+        if iotests.qemu_default_machine != 'pc':
+            return
+
         result = self.vm.qmp('drive-mirror', device='ide1-cd0', sync='full',
                              node_name='repair0',
                              replaces='img1',
-- 
2.3.0

  parent reply	other threads:[~2015-05-22  1:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22  1:26 [Qemu-devel] [PATCH RFC v9 0/7] Update tests/qemu-iotests failing cases for the s390 platform Bo Tu
2015-05-22  1:26 ` [Qemu-devel] [PATCH RFC v9 1/7] qemu-iotests: qemu machine type support Bo Tu
2015-05-22  1:26 ` [Qemu-devel] [PATCH RFC v9 2/7] qemu-iotests: run qemu with -nodefaults and fix 067, 071, 081 and 087 Bo Tu
2015-05-22  1:26 ` Bo Tu [this message]
2015-05-22  1:26 ` [Qemu-devel] [PATCH RFC v9 4/7] qemu-iotests: s390x: fix test 055 Bo Tu
2015-05-22  1:26 ` [Qemu-devel] [PATCH RFC v9 5/7] qemu-iotests: s390x: fix test 049 Bo Tu
2015-05-23 17:52   ` Max Reitz
2015-05-22  1:26 ` [Qemu-devel] [PATCH RFC v9 6/7] qemu-iotests: s390x: fix test 051 Bo Tu
2015-05-22  1:26 ` [Qemu-devel] [PATCH RFC v9 7/7] qemu-iotests: s390x: fix test 130 Bo Tu
  -- strict thread matches above, loose matches on Subject: below --
2015-05-25  3:30 [Qemu-devel] [PATCH RFC v9 0/7] Update tests/qemu-iotests failing cases for the s390 platform Bo Tu
2015-05-25  3:30 ` [Qemu-devel] [PATCH RFC v9 3/7] qemu-iotests: s390x: fix test 041 Bo Tu

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=1432257981-10411-4-git-send-email-tubo@linux.vnet.ibm.com \
    --to=tubo@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).