selftests: mptcp: connect: fail if nft supposed to work
authorMatthieu Baerts <matthieu.baerts@tessares.net>
Tue, 4 Jul 2023 20:44:35 +0000 (22:44 +0200)
committerDavid S. Miller <davem@davemloft.net>
Wed, 5 Jul 2023 09:51:14 +0000 (10:51 +0100)
commit221e4550454a822f9a11834e30694c7d1d65747c
tree1af6560dc8f739bb6face8b698df441f6e1da100
parent0226436acf2495cde4b93e7400e5a87305c26054
selftests: mptcp: connect: fail if nft supposed to work

In case of "external" errors when preparing the environment for the
TProxy tests, the subtests were marked as skipped.

This is fine but it means these errors are ignored. On MPTCP Public CI,
we do want to catch such issues and mark the selftest as failed if there
are such issues. We can then use mptcp_lib_fail_if_expected_feature()
helper that has been recently added to fail if needed.

Link: https://github.com/multipath-tcp/mptcp_net-next/issues/368
Fixes: 5fb62e9cd3ad ("selftests: mptcp: add tproxy test case")
Cc: stable@vger.kernel.org
Acked-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
tools/testing/selftests/net/mptcp/mptcp_connect.sh