On 16/07/2025 17:36, Jakub Kicinski wrote: > 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-99a3cafd3...@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%.
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. Cheers, Matt -- Sponsored by the NGI0 Core fund.
