From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL v3 41/41] iotests: Check for quorum support in test 139
Date: Wed, 11 Nov 2015 17:08:44 +0100 [thread overview]
Message-ID: <1447258124-32577-4-git-send-email-kwolf@redhat.com> (raw)
In-Reply-To: <1447258124-32577-1-git-send-email-kwolf@redhat.com>
From: Alberto Garcia <berto@igalia.com>
The quorum driver is always built in, but it is disabled during
run-time if there's no SHA256 support available (see commit e94867e).
This patch skips the quorum test in iotest 139 in that case.
Signed-off-by: Alberto Garcia <berto@igalia.com>
Message-id: 1447172891-20410-1-git-send-email-berto@igalia.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
---
tests/qemu-iotests/139 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/qemu-iotests/139 b/tests/qemu-iotests/139
index b5470f7..42f78c7 100644
--- a/tests/qemu-iotests/139
+++ b/tests/qemu-iotests/139
@@ -400,6 +400,8 @@ class TestBlockdevDel(iotests.QMPTestCase):
self.checkBlockDriverState('node1', False)
def testQuorum(self):
+ if not 'quorum' in iotests.qemu_img_pipe('--help'):
+ return
self.addQuorum('quorum0', 'node0', 'node1')
# We cannot remove the children of a Quorum device
self.delBlockDriverState('node0', expect_error = True)
--
1.8.3.1
next prev parent reply other threads:[~2015-11-11 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 16:08 [Qemu-devel] [PULL v3 00/41] Block layer patches Kevin Wolf
2015-11-11 16:08 ` [Qemu-devel] [PULL v3 14/41] blockdev: read-only-mode for blockdev-change-medium Kevin Wolf
2015-11-11 16:08 ` [Qemu-devel] [PULL v3 31/41] qemu-io: fix cvtnum lval types Kevin Wolf
2015-11-11 16:08 ` Kevin Wolf [this message]
2015-11-11 18:22 ` [Qemu-devel] [PULL v3 00/41] Block layer patches Peter Maydell
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=1447258124-32577-4-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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).