On Mon, 29 Jan 2024 17:31:33 +0100 Paolo Abeni wrote: > Uhm... while the self-test doesn't emit anymore the message related to > the missing modules, it still fails in the CI env and I can't reproduce > the failures in my local env (the same for the gro.sh script). > > If I understand correctly, the tests run under double virtualization (a > VM on top AWS?), is that correct? I guess the extra slowdown/overhead > will need more care. Yes, it's VM inside a VM without nested virtualization support. A weird setup, granted, but when we move to bare metal I'd like to enable KASAN, which will probably cause a similar slowdown.. You could possibly get a similar slowdown by disabling HW virt / KVM? FWIW far the 4 types of issues we've seen were: - config missing - OS doesn't ifup by default - OS tools are old / buggy - VM-in-VM is just too slow. There's a bunch of failures in forwarding which look like perf issues. I wonder if we should introduce something in the settings file to let tests know that they are running in very slow env?
