[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76d0de38-aff5-41e9-8085-afeb97b4d4f4@kernel.org>
Date: Thu, 26 Sep 2024 11:12:25 +0200
From: Matthieu Baerts <matttbe@...nel.org>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>, netdev@...r.kernel.org
Cc: davem@...emloft.net, kuba@...nel.org, edumazet@...gle.com,
pabeni@...hat.com, sdf@...ichev.me, linux-kselftest@...r.kernel.org,
Willem de Bruijn <willemb@...gle.com>
Subject: Re: [PATCH net] selftests/net: packetdrill: increase timing tolerance
in debug mode
Hi Willem,
On 20/09/2024 00:03, Matthieu Baerts wrote:
> On 19/09/2024 14:43, Willem de Bruijn wrote:
>> From: Willem de Bruijn <willemb@...gle.com>
(...)
>> We have been doing this for debug builds outside ksft too.
>>
>> Previous setting was 10000. A manual 50 runs in virtme-ng showed two
>> failures that needed 12000. To be on the safe side, Increase to 14000.
>
> So far (in 3 runs), it looks like 14000 is enough. But I guess it is
> still a bit too early to conclude that.
>
> https://netdev.bots.linux.dev/contest.html?executor=vmksft-packetdrill-dbg
>
> (Your patch has been introduced in the net-next-2024-09-19--15-00 branch.)
One week after the introduction of this patch and >50 builds, it looks
like the results are good, only one issue related to timing issues:
https://netdev-3.bots.linux.dev/vmksft-packetdrill-dbg/results/782181/1-tcp-slow-start-slow-start-after-win-update-pkt/stdout
And it passed after a retry.
https://netdev.bots.linux.dev/flakes.html?min-flip=0&tn-needle=packetdrill
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
Powered by blists - more mailing lists