gro.py runs its full set of cases three times over - against SW GRO, HW GRO and LRO. It's our test with the longest runtime. The 318 cases take 12m30s on mlx5 with a debug kernel.
We will likely add more subcases here as the time goes on, so it's time to start splitting it up. Long runtime wastes time on retries (if any of the 300+ cases fails we try to check if it's a real failure or flake an re-run the whole thing). It also forces us to increase timeout for the whole test suite. v2: - [patch 2] reorder import lines to make ruff check happy v1: https://lore.kernel.org/[email protected] Jakub Kicinski (3): selftests: drv-net: hw: rename gro_hw.py to gro_stats.py selftests: drv-net: split gro.py into one test per coalescing mode selftests: drv-net: bump the timeout to 15min tools/testing/selftests/drivers/net/Makefile | 9 ++- .../testing/selftests/drivers/net/hw/Makefile | 2 +- tools/testing/selftests/drivers/net/gro_hw.py | 13 ++++ .../drivers/net/{gro.py => gro_lib.py} | 68 +++++++++---------- .../testing/selftests/drivers/net/gro_lro.py | 14 ++++ tools/testing/selftests/drivers/net/gro_sw.py | 13 ++++ .../net/hw/{gro_hw.py => gro_stats.py} | 0 .../selftests/drivers/net/pppoe_gro.py | 45 ++++++++++++ tools/testing/selftests/drivers/net/settings | 2 +- .../selftests/net/lib/ksft_setup_loopback.sh | 2 +- 10 files changed, 127 insertions(+), 41 deletions(-) create mode 100755 tools/testing/selftests/drivers/net/gro_hw.py rename tools/testing/selftests/drivers/net/{gro.py => gro_lib.py} (92%) mode change 100755 => 100644 create mode 100755 tools/testing/selftests/drivers/net/gro_lro.py create mode 100755 tools/testing/selftests/drivers/net/gro_sw.py rename tools/testing/selftests/drivers/net/hw/{gro_hw.py => gro_stats.py} (100%) create mode 100755 tools/testing/selftests/drivers/net/pppoe_gro.py -- 2.55.0
