On Fri, 12 Jan 2024 20:10:56 +0000 luca.bocca...@gmail.com wrote: > From: Luca Boccassi <bl...@debian.org> > > These tests are failing with timeouts on build machines with large amount > of cores, so move them out of the fast suite, which should complete in > seconds. > > 33/77 DPDK:fast-tests / lcores_autotest TIMEOUT 50.01s > https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_11/aarch64 > > 43/77 DPDK:fast-tests / pdump_autotest TIMEOUT 120.11s > killed by signal 15 SIGTERM > https://ci.debian.net/packages/d/dpdk/unstable/ppc64el/41544027/#S10 > > 45/77 DPDK:fast-tests / pflock_autotest TIMEOUT 120.14s > killed by signal 15 SIGTERM > 72/77 DPDK:fast-tests / ticketlock_autotest TIMEOUT 120.12s > killed by signal 15 SIGTERM > https://ci.debian.net/packages/d/dpdk/unstable/amd64/41560884/#S10 > > Signed-off-by: Luca Boccassi <bl...@debian.org>
Moving the test makes sense but having it dangling causes new warnings. app/test/suites/meson.build:35: WARNING: Test "pflock_autotest" is not defined in any test suite app/test/suites/meson.build:35: WARNING: Test "ticketlock_autotest" is not defined in any test suite Maybe increase the timeout or add to perf test suite instead?
