[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250716083632.72854bd5@kernel.org>
Date: Wed, 16 Jul 2025 08:36:32 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Matthieu Baerts <matttbe@...nel.org>
Cc: mptcp@...ts.linux.dev, Mat Martineau <martineau@...nel.org>, Geliang
Tang <geliang@...nel.org>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Simon
Horman <horms@...nel.org>, Shuah Khan <shuah@...nel.org>, Christoph Paasch
<cpaasch@...nai.com>, Davide Caratti <dcaratti@...hat.com>, Florian
Westphal <fw@...len.de>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-kselftest@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH net v2 0/2] selftests: mptcp: connect: cover alt modes
On Wed, 16 Jul 2025 16:55:21 +0200 Matthieu Baerts wrote:
> >> Looks like the failures that Paolo flagged yesterday:
> >>
> >> https://lore.kernel.org/all/a7a89aa2-7354-42c7-8219-99a3cafd3b33@redhat.com/
> >>
> >> are back as soon as this hit NIPA :(
> >>
> >> https://netdev.bots.linux.dev/contest.html?branch=net-next-2025-07-16--00-00&executor=vmksft-mptcp&pw-n=0&pass=0
> >>
> >> No idea why TBH, the tests run sequentially and connect.sh run before
> >> any of the new ones.
>
> And just to be sure, no CPU or IO overload at that moment? I didn't see
> such errors reported by our CI, but I can try to reproduce them locally
> in different conditions.
None that I can see. The test run ~10min after all the builds completed,
and we wait now for the CPU load to die down and writeback to finish
before we kick off VMs. The VMs for various tests are running at that
point, the CPU util averaged across cores is 66%.
Powered by blists - more mailing lists