WSL2-Linux-Kernel/tools/testing
Matthieu Baerts a4debc4772 selftests: mptcp: display proper reason to abort tests
Without this modification, we were often displaying this error messages:

  FAIL: Could not even run loopback test

But $ret could have been set to a non 0 value in many different cases:

- net.mptcp.enabled=0 is not working as expected
- setsockopt(..., TCP_ULP, "mptcp", ...) is allowed
- ping between each netns are failing
- tests between ns1 as a receiver and ns>1 are failing
- other tests not involving ns1 as a receiver are failing

So not only for the loopback test.

Now a clearer message, including the time it took to run all tests, is
displayed.

Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2021-06-22 09:57:45 -07:00
..
fault-injection
ktest
kunit
nvdimm
radix-tree
scatterlist
selftests selftests: mptcp: display proper reason to abort tests 2021-06-22 09:57:45 -07:00
vsock vsock_test: add SOCK_SEQPACKET tests 2021-06-11 13:32:47 -07:00