From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
MPTCP Upstream <mptcp@lists.linux.dev>,
Paolo Abeni <pabeni@redhat.com>,
Mat Martineau <martineau@kernel.org>
Subject: Re: [TEST] The no-kvm CI instances going away
Date: Wed, 7 Feb 2024 15:37:22 +0100 [thread overview]
Message-ID: <e216081b-8755-46be-a687-2c61d335aedb@kernel.org> (raw)
In-Reply-To: <20240207062540.5fe5563b@kernel.org>
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.
next prev parent reply other threads:[~2024-02-07 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 1:41 [TEST] The no-kvm CI instances going away Jakub Kicinski
2024-02-06 11:16 ` Matthieu Baerts
2024-02-07 1:44 ` Jakub Kicinski
2024-02-07 9:44 ` Matthieu Baerts
2024-02-07 14:25 ` Jakub Kicinski
2024-02-07 14:37 ` Matthieu Baerts [this message]
2024-02-07 15:29 ` Jakub Kicinski
2024-02-07 16:06 ` Matthieu Baerts
2024-02-07 17:45 ` David Ahern
2024-02-07 18:55 ` Jakub Kicinski
2024-02-07 19:45 ` David Ahern
2024-02-07 20:07 ` Jakub Kicinski
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=e216081b-8755-46be-a687-2c61d335aedb@kernel.org \
--to=matttbe@kernel.org \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).