[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: make -j check failing on master, interesting valgrind errors on qos-
From: |
Claudio Fontana |
Subject: |
Re: make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic |
Date: |
Fri, 27 May 2022 12:10:45 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 |
On 5/27/22 10:18 AM, Claudio Fontana wrote:
> On 5/27/22 9:26 AM, Dario Faggioli wrote:
>> On Thu, 2022-05-26 at 20:18 +0200, Claudio Fontana wrote:
>>> Forget about his aspect, I think it is a separate problem.
>>>
>>> valgind of qos-test when run restricted to those specific paths (-p
>>> /x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-net-pci/virtio-
>>> net/virtio-net-tests/vhost-user/reconnect for example)
>>> shows all clear,
>>>
>>> and still the test fails when run in a while loop after a few
>>> attempts:
>>>
>> Yes, this kind of matches what I've also seen and reported about in
>> <5bcb5ceb44dd830770d66330e27de6a4345fcb69.camel@suse.com>. If
>> enable/run just one of:
>> - reconnect
>> - flags_mismatch
>> - connect_fail
>>
>> I see no issues.
>
> On the countrary, for me just running a single one of those can fail.
>
> To reproduce this I run in a loop using, as quoted above,
>
> -p
> /x86_64/pc/i440FX-pcihost/pci-bus-pc/pci-bus/virtio-net-pci/virtio-net/virtio-net-tests/vhost-user/reconnect
>
>
> for example.
>
> After a few successful runs I hit the error.
>
>
>>
>> As soon as two of those are run, one after the other, the problem
>> starts to appear.
>
> Not for me: one is enough.
>
>>
>> However, Claudio, AFAIUI, you're seeing this with an older GCC and
>> without LTO, right?
>
> Yes, to provide a different angle I tried on veteran OpenSUSE Leap 15.2, so
> gcc is based on 7.5.0.
>
> I don't think LTO is being used in any way.
>
>>
>> Regards
>>
>
> Ciao,
>
> CLaudio
>
Hi Alex, I noticed that the asserts in wait_for_rings_started and such are
triggered after
the timeout of 5 seconds passed (end_time = g_get_monotonic_time() + 5 *
G_TIME_SPAN_SECOND).
I tried to increase the timeouts from 5 seconds to 30 seconds
(tests/qtest/vhost-user-test.c)
Still the thing timeouts.
Do we have there a problem with the data_mutex or the signaling of the
condition variable?
Ciao,
Claudio
- make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic, Claudio Fontana, 2022/05/26
- Re: make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic, Claudio Fontana, 2022/05/26
- Re: make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic, Dario Faggioli, 2022/05/27
- Re: make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic, Claudio Fontana, 2022/05/27
- Re: make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic,
Claudio Fontana <=
- Re: make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic, Dario Faggioli, 2022/05/27
- Re: make -j check failing on master, interesting valgrind errors on qos-test vhost-user-blk-test/basic, Alex Bennée, 2022/05/27