Hi Jakub,
On 17/07/2025 16:42, Jakub Kicinski wrote:
On Wed, 16 Jul 2025 18:35:11 +0200 Matthieu Baerts wrote:
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%.
Thank you for having checked, and for the explanations!
OK, so maybe running stress-ng in parallel to be able to reproduce the issue might not help. We will investigate.
connect tests failed again overnight. Now I see why Paolo was responding on Eric's series, that seems like a more likely culprit..
Good point, Paolo was certainly right, as always :)
We do need to investigate. Note that it might be hard for me to do that the next few days as I'm travelling for work, but we are tracking the issue:
https://github.com/multipath-tcp/mptcp_net-next/issues/574
I see that you already marked the mptcp-connect-sh selftest as ignored, so I guess we are not causing other troubles with the CI. (We could then also apply this series here and ignore the new tests, but it is also fine for me to wait.)
Cheers, Matt