From: Claudio Fontana <cfontana@suse.de>
To: "Vladimir Sementsov-Ogievskiy" <vsementsov@virtuozzo.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Qemu-block <qemu-block@nongnu.org>
Subject: Re: iotest 30 failing
Date: Fri, 5 Feb 2021 12:00:04 +0100 [thread overview]
Message-ID: <b5e61c20-f500-b1cd-daa4-bdb9a368cb96@suse.de> (raw)
In-Reply-To: <5c0ffc79-aabc-1b40-8758-9840845432bf@virtuozzo.com>
On 2/4/21 11:38 PM, Vladimir Sementsov-Ogievskiy wrote:
> 04.02.2021 20:51, Peter Maydell wrote:
>> On Thu, 4 Feb 2021 at 17:48, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>>
>>> Hi,
>>>
>>> Based on commit 1ed9228f63e (ericb/tags/pull-nbd-2021-02-02-v2)
>>> I got:
>>>
>>> TEST iotest-qcow2: 030 [fail]
>>
>> Yes; see also this thread:
>> https://lore.kernel.org/qemu-devel/9e71568c-ce4a-f844-fbd3-a4a59f850d74@redhat.com/
>>
>> Can somebody write a simple patch to disable the test entirely,
>> please? It's too unreliable to be in our CI set.
>>
>
> I can..
>
> Still, maybe I'll try tomorrow to make v2 from my "[PATCH RFC 0/5] Fix accidental crash in iotest 30"?
>
> It would be very interesting will it fail after that fix. My experiments shows that my patches helps. But the question is do we really have the same crash in all these reports or not. So I think it worth taking my fix (even being incomplete solution) to understand do we ignore some unknown bug.
>
Today's master passes the test for me, yesterday's failed. Was something changed or is it just flicky..
Ciao,
Claudio
prev parent reply other threads:[~2021-02-05 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 16:47 iotest 30 failing Philippe Mathieu-Daudé
2021-02-04 17:51 ` Peter Maydell
2021-02-04 22:38 ` Vladimir Sementsov-Ogievskiy
2021-02-05 11:00 ` Claudio Fontana [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=b5e61c20-f500-b1cd-daa4-bdb9a368cb96@suse.de \
--to=cfontana@suse.de \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).