From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, berrange@redhat.com, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] iotests: Skip 233 if certtool not installed
Date: Tue, 20 Nov 2018 18:22:56 -0500 [thread overview]
Message-ID: <5ce9a65a-4d82-c001-2fff-b6158e159d2f@redhat.com> (raw)
In-Reply-To: <20181120225241.2371769-1-eblake@redhat.com>
On 11/20/18 5:52 PM, Eric Blake wrote:
> The use of TLS while building qemu is optional. While the
> 'certtool' binary should be available on every platform that
> supports building against TLS, that does not imply that the
> developer has installed it. Make the test gracefully skip
> in that case.
>
> Reported-by: Kevin Wolf <kwolf@redhat.com>
> Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
> ---
>
> On Fedora, libvirt requires libtls-utils to be present, but not qemu.
>
> I'm fine if Kevin wants to pick this up in a pull request related
> to iotests in general; if not, I'll do a pull request through my
> NBD tree in time for -rc3.
>
> tests/qemu-iotests/common.tls | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/qemu-iotests/common.tls b/tests/qemu-iotests/common.tls
> index 39f17c1b999..eae81789bbc 100644
> --- a/tests/qemu-iotests/common.tls
> +++ b/tests/qemu-iotests/common.tls
> @@ -31,6 +31,9 @@ tls_x509_cleanup()
>
> tls_x509_init()
> {
> + (certtool --help) >/dev/null 2>&1 || \
> + _notrun "certtool utility not found, skipping test"
> +
Or something wickedly foul has happened :)
> mkdir -p "${tls_dir}"
>
> # use a fixed key so we don't waste system entropy on
>
next prev parent reply other threads:[~2018-11-20 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 22:52 [Qemu-devel] [PATCH] iotests: Skip 233 if certtool not installed Eric Blake
2018-11-20 23:11 ` Eric Blake
2018-11-20 23:22 ` John Snow [this message]
2018-11-21 9:31 ` Kevin Wolf
2018-11-21 9:32 ` Daniel P. Berrangé
2018-11-21 12:06 ` Wainer dos Santos Moschetta
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=5ce9a65a-4d82-c001-2fff-b6158e159d2f@redhat.com \
--to=jsnow@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).