From: Jing Liu <liujbjl@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question for iotests 188, 189 and 087
Date: Wed, 19 Jul 2017 10:40:11 +0800 [thread overview]
Message-ID: <6e17b13f-e903-2073-409c-2442c734251d@linux.vnet.ibm.com> (raw)
In-Reply-To: <93a523dc-0cf4-c73b-518d-ef48e9f8ca64@redhat.com>
Hi Eric,
On 2017/7/18 下午10:57, Eric Blake wrote:
> On 07/17/2017 10: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.
> It might help to show the ./check command line you are using, as well as
> the errors you are getting. Right now, master is failing on 51, 140,
> and 143 when I test across './check -raw', './check -qcow2', and
> './check nbd',
I used ./check -qcow2 to do it.
I tested on different machines and got different results. One is failed
on 140 and 143. The other one told
me 087, 140, 143, 188, 189.
I guess it is because some configuration or libraries, and will also
refer to other replies from the mail.
I'll check the details.
Thank you so much.
Jing
> but not the three you mention. But the iotests framework
> allows a lot more combinations of testing (and we probably have some
> lurking testsuite bugs on some of the more exotic combinations).
>
next prev parent reply other threads:[~2017-07-19 2:40 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 [this message]
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
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=6e17b13f-e903-2073-409c-2442c734251d@linux.vnet.ibm.com \
--to=liujbjl@linux.vnet.ibm.com \
--cc=eblake@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).