From: Matthieu Baerts <matttbe@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Netdev <netdev@vger.kernel.org>, MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [TEST] mptcp-connect
Date: Mon, 13 Jan 2025 17:08:02 +0100 [thread overview]
Message-ID: <22a1d42b-3015-47cf-b3d9-46d0ceb63ebc@kernel.org> (raw)
In-Reply-To: <1ac62b6e-ee3d-499a-8817-f7cdfd2f2db5@kernel.org>
Hi Jakub,
On 08/01/2025 11:07, Matthieu Baerts wrote:
> Hi Jakub,
>
> (+cc MPTCP list)
>
> On 07/01/2025 22:18, Jakub Kicinski wrote:
>> Unfortunately mptcp_connect.sh has started flaking again :(
>> Looks like it started around Dec 30th, so one of the recent PRs
>
> Thank you for the heads-up!
>
> After the last PR, I was focussing on monitoring simult_flows.sh -- the
> recent behaviour changes could have affected it -- and forgot to look at
> the others, sorry about that...
>
> It looks like our CI doesn't have this issue, but the builds are less
> frequent [1]. I'm going to investigate that ASAP.
It was not easy to reproduce it, but Paolo managed to find a fix for it [1]!
Out of curiosity, is the netdev CI not too overloaded? To reproduce this
issue on my side, the host had to be quite busy: not dying with
stress-ng using all resources, but still competing with many other
processes, e.g. a kernel compilation running in parallel. I'm not
complaining here, because this situation helped finding this important
issue, but just curious about what to expect, especially for more
"sensitive" tests :)
On the MPTCP CI, some unessarry KConfig are disabled and ccache is used
to reduce the build time. Also, RETPOLINE is disabled (+ vng --append
mitigations=off) to save some CPU cycles during the tests.
[1]
https://lore.kernel.org/netdev/20250113-net-mptcp-connect-st-flakes-v1-0-0d986ee7b1b6@kernel.org/T/
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-01-13 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250107131845.5e5de3c5@kernel.org>
2025-01-08 10:07 ` [TEST] mptcp-connect Matthieu Baerts
2025-01-13 16:08 ` Matthieu Baerts [this message]
2025-01-13 19:44 ` Jakub Kicinski
2025-01-14 14:18 ` Matthieu Baerts
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=22a1d42b-3015-47cf-b3d9-46d0ceb63ebc@kernel.org \
--to=matttbe@kernel.org \
--cc=kuba@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/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