mbox series

[net-next,v3,0/8] selftests: drv-net: support testing with a remote system

Message ID 20240417231146.2435572-1-kuba@kernel.org (mailing list archive)
Headers show
Series selftests: drv-net: support testing with a remote system | expand

Message

Jakub Kicinski April 17, 2024, 11:11 p.m. UTC
Hi!

Implement support for tests which require access to a remote system /
endpoint which can generate traffic.
This series concludes the "groundwork" for upstream driver tests.

I wanted to support the three models which came up in discussions:
 - SW testing with netdevsim
 - "local" testing with two ports on the same system in a loopback
 - "remote" testing via SSH
so there is a tiny bit of an abstraction which wraps up how "remote"
commands are executed. Otherwise hopefully there's nothing surprising.

I'm only adding a ping test. I had a bigger one written but I was
worried we'll get into discussing the details of the test itself
and how I chose to hack up netdevsim, instead of the test infra...
So that test will be a follow up :)

v3:
 - first two patches are new
 - make Remote::cmd() return Popen() object (patch 3)
 - always operate on absolute paths (patch 3)
 - last two patches are new
v2: https://lore.kernel.org/all/20240416004556.1618804-1-kuba@kernel.org
 - rename endpoint -> remote
 - use 2001:db8:: v6 prefix
 - add a note about persistent SSH connections
 - add the kernel config
v1: https://lore.kernel.org/all/20240412233705.1066444-1-kuba@kernel.org

Jakub Kicinski (8):
  selftests: net: fix counting totals when some checks fail
  selftests: net: set the exit code correctly in Python tests
  selftests: drv-net: define endpoint structures
  selftests: drv-net: factor out parsing of the env
  selftests: drv-net: construct environment for running tests which
    require an endpoint
  selftests: drv-net: add a trivial ping test
  selftests: net: support matching cases by name prefix
  selftests: drv-net: add a TCP ping test case (and useful helpers)

 tools/testing/selftests/drivers/net/Makefile  |   5 +-
 .../testing/selftests/drivers/net/README.rst  |  33 ++++
 .../selftests/drivers/net/lib/py/__init__.py  |   1 +
 .../selftests/drivers/net/lib/py/env.py       | 141 +++++++++++++++---
 .../selftests/drivers/net/lib/py/remote.py    |  15 ++
 .../drivers/net/lib/py/remote_netns.py        |  21 +++
 .../drivers/net/lib/py/remote_ssh.py          |  39 +++++
 tools/testing/selftests/drivers/net/ping.py   |  52 +++++++
 tools/testing/selftests/drivers/net/stats.py  |   4 +-
 .../testing/selftests/net/lib/py/__init__.py  |   1 +
 tools/testing/selftests/net/lib/py/ksft.py    |  25 +++-
 tools/testing/selftests/net/lib/py/netns.py   |  31 ++++
 tools/testing/selftests/net/lib/py/utils.py   |  50 ++++++-
 tools/testing/selftests/net/nl_netdev.py      |   4 +-
 14 files changed, 391 insertions(+), 31 deletions(-)
 create mode 100644 tools/testing/selftests/drivers/net/lib/py/remote.py
 create mode 100644 tools/testing/selftests/drivers/net/lib/py/remote_netns.py
 create mode 100644 tools/testing/selftests/drivers/net/lib/py/remote_ssh.py
 create mode 100755 tools/testing/selftests/drivers/net/ping.py
 create mode 100644 tools/testing/selftests/net/lib/py/netns.py

Comments

patchwork-bot+netdevbpf@kernel.org April 18, 2024, 11:20 p.m. UTC | #1
Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 17 Apr 2024 16:11:38 -0700 you wrote:
> Hi!
> 
> Implement support for tests which require access to a remote system /
> endpoint which can generate traffic.
> This series concludes the "groundwork" for upstream driver tests.
> 
> I wanted to support the three models which came up in discussions:
>  - SW testing with netdevsim
>  - "local" testing with two ports on the same system in a loopback
>  - "remote" testing via SSH
> so there is a tiny bit of an abstraction which wraps up how "remote"
> commands are executed. Otherwise hopefully there's nothing surprising.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/8] selftests: net: fix counting totals when some checks fail
    https://git.kernel.org/netdev/net-next/c/655614ea2bd3
  - [net-next,v3,2/8] selftests: net: set the exit code correctly in Python tests
    https://git.kernel.org/netdev/net-next/c/4fa6bd4b33ac
  - [net-next,v3,3/8] selftests: drv-net: define endpoint structures
    (no matching commit)
  - [net-next,v3,4/8] selftests: drv-net: factor out parsing of the env
    (no matching commit)
  - [net-next,v3,5/8] selftests: drv-net: construct environment for running tests which require an endpoint
    (no matching commit)
  - [net-next,v3,6/8] selftests: drv-net: add a trivial ping test
    (no matching commit)
  - [net-next,v3,7/8] selftests: net: support matching cases by name prefix
    (no matching commit)
  - [net-next,v3,8/8] selftests: drv-net: add a TCP ping test case (and useful helpers)
    (no matching commit)

You are awesome, thank you!