[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: iotest 30 failing
|
From: |
Claudio Fontana |
|
Subject: |
Re: iotest 30 failing |
|
Date: |
Fri, 5 Feb 2021 12:00:04 +0100 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 |
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:
>> 9e71568c-ce4a-f844-fbd3-a4a59f850d74@redhat.com/">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