From: Jing Liu <liujbjl@linux.vnet.ibm.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: Cleber Rosa <crosa@redhat.com>, Lukas Doktor <ldoktor@redhat.com>,
Amador Segundo <asegundo@redhat.com>
Subject: Re: [Qemu-devel] Question for iotests 188, 189 and 087
Date: Wed, 19 Jul 2017 15:27:39 +0800 [thread overview]
Message-ID: <b77f50e6-e8ce-75c3-bd1e-7cae3a4cee68@linux.vnet.ibm.com> (raw)
In-Reply-To: <96e5169c-6149-fd7a-3347-0994089e01ac@redhat.com>
On 2017/7/19 上午2:07, John Snow wrote:
>
> On 07/17/2017 11:01 PM, Jing Liu wrote:
>> Hi all,
>>
>> Do you anybody have iotests failure: 188, 189 and 087 of the latest qemu
>> upsteam?
>>
>> I just wondered if it has something wrong with my test machines because
>> I have different results with two machines.
>>
>>
>> Thanks.
>>
>> Jing
>>
>>
> Presumably you are missing aio=native support for 087,
>
> and 188/189 I believe require compression and/or LUKS libraries.
Hi John,
Yes, I indeed miss some crypto libraries.
Thank you for your support. Now all of them are fixed.
Jing
> These are false positives caused by missing libraries. We should
> probably work out a proper solution to meaningfully skipping tests we
> didn't compile support for.
>
> --js
>
prev parent reply other threads:[~2017-07-19 7:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 3:01 [Qemu-devel] Question for iotests 188, 189 and 087 Jing Liu
2017-07-18 14:57 ` Eric Blake
2017-07-19 2:40 ` Jing Liu
2017-07-18 18:07 ` John Snow
2017-07-18 21:22 ` Cleber Rosa
2017-07-18 21:47 ` John Snow
2017-07-19 16:12 ` Cleber Rosa
2017-07-18 22:16 ` Eric Blake
2017-07-20 8:37 ` Jing Liu
2017-07-20 13:52 ` Cleber Rosa
2017-07-19 7:27 ` Jing Liu [this message]
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=b77f50e6-e8ce-75c3-bd1e-7cae3a4cee68@linux.vnet.ibm.com \
--to=liujbjl@linux.vnet.ibm.com \
--cc=asegundo@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=ldoktor@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).