From: Eric Blake <eblake@redhat.com>
To: Peter Xu <peterx@redhat.com>, John Snow <jsnow@redhat.com>,
Fam Zheng <famz@redhat.com>, Max Reitz <mreitz@redhat.com>
Cc: Qemu-block <qemu-block@nongnu.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] raw iotest regressions in 2.12.0-rc0
Date: Fri, 23 Mar 2018 17:02:30 -0500 [thread overview]
Message-ID: <e45efdc6-e43c-8af5-3a94-2f02fecc07e1@redhat.com> (raw)
In-Reply-To: <20180322135443.GJ32362@xz-mi>
On 03/22/2018 08:54 AM, Peter Xu wrote:
> On Wed, Mar 21, 2018 at 05:58:48PM -0400, John Snow wrote:
>> ./check -v -raw
>> Failures: 109 132 136 148 152 183
>>
>>
>> ./check -v raw
>> Failures: 055
>> Failed 5 of 5 tests
>>
>> Maybe these are known, but I wanted to consolidate them for rc0 for
>> something easy to search for. There are others for qcow2 which I'll post
>> in a bit...!
I think patches have been floating on list for the failures in 51, 185,
and 186 under qcow2, which were failing independently of the OOB changes.
>>
>>
>> Thanks,
>> --js
>
> CCing Max, Fam.
>
> Now I think I know how to solve some of the tests already (109, 132,
> 148, 152, 183). While I am still working (or, not yet started to work)
> on some others (055, 136, 205).
>
> 205 is interesting - it won't fail every time, but randomly:
>
>
> While I haven't started to look at 055, which is:
>
> I'll continue and update tomorrow. So if anyone has any idea on
> solving any of the problem, please feel free to shoot.
>
Let me know how I can help, as well.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-03-23 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 21:58 [Qemu-devel] raw iotest regressions in 2.12.0-rc0 John Snow
2018-03-22 3:25 ` Peter Xu
2018-03-22 13:54 ` Peter Xu
2018-03-23 22:02 ` Eric Blake [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=e45efdc6-e43c-8af5-3a94-2f02fecc07e1@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=peterx@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).