[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e216081b-8755-46be-a687-2c61d335aedb@kernel.org>
Date: Wed, 7 Feb 2024 15:37:22 +0100
From: Matthieu Baerts <matttbe@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
MPTCP Upstream <mptcp@...ts.linux.dev>, Paolo Abeni <pabeni@...hat.com>,
Mat Martineau <martineau@...nel.org>
Subject: Re: [TEST] The no-kvm CI instances going away
On 07/02/2024 15:25, Jakub Kicinski wrote:
> On Wed, 7 Feb 2024 10:44:14 +0100 Matthieu Baerts wrote:
>>> Unfortunately I'm really behind on my "real job". I don't have a clear
>>> plan. I think we should scale the timeout by 2x or so, but I haven't
>>> looked how to do that.
>>
>> No hurry, I understand.
>>
>> It is not clear to me how the patches you add on top of the ones from
>> patchwork are managed. Then, I don't know if it can help, but on the
>> debug instance, this command could be launched before starting the tests
>> to double the timeout values in all the "net" selftests:
>>
>> $ find tools/testing/selftests/net -name settings -print0 | xargs -0 \
>> awk -i inplace -F '=' \
>> '{if ($1 == "timeout") { print $1 "=" $2*2 } else { print }}'
>
> I'd rather not modify the tree. Poking around - this seems to work:
>
> export kselftest_override_timeout=1
Even better :)
f=tools/testing/selftests/net/settings
kselftest_override_timeout=$(awk -F = '/^timeout=/ {print $2*2}' $f)
> Now it's just a matter of finding 15min to code it up :)
I'm not sure if I can help here :)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
Powered by blists - more mailing lists