[PATCH mptcp-next 0/2] selftests: mptcp: some improvement for selftests

Gang Yan posted 2 patches 23 hours ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/20260724065229.36736-1-gang.yan@linux.dev
tools/testing/selftests/net/mptcp/mptcp_join.sh   | 4 ++--
tools/testing/selftests/net/mptcp/simult_flows.sh | 3 +--
2 files changed, 3 insertions(+), 4 deletions(-)
[PATCH mptcp-next 0/2] selftests: mptcp: some improvement for selftests
Posted by Gang Yan 23 hours ago
From: Gang Yan <yangang@kylinos.cn>

This series contains two independent selftest fixes. Both are about
making failures correctly handled instead of being silently masked or
leaving resources behind. They are unrelated and can be applied/merged
independently.

Gang Yan (2):
  selftests: mptcp: run fail_test in main shell during join test
  selftests: mptcp: simult_flows: set EXIT trap earlier

 tools/testing/selftests/net/mptcp/mptcp_join.sh   | 4 ++--
 tools/testing/selftests/net/mptcp/simult_flows.sh | 3 +--
 2 files changed, 3 insertions(+), 4 deletions(-)

-- 
2.43.0
Re: [PATCH mptcp-next 0/2] selftests: mptcp: some improvement for selftests
Posted by MPTCP CI 22 hours ago
Hi Gang,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: normal (except selftest_mptcp_join): Success! ✅
- KVM Validation: normal (only selftest_mptcp_join): Success! ✅
- KVM Validation: debug (except selftest_mptcp_join): Success! ✅
- KVM Validation: debug (only selftest_mptcp_join): Success! ✅
- KVM Validation: btf-normal (only bpftest_all): Success! ✅
- KVM Validation: btf-debug (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/30074599252

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/1a463b49605d
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=1133691


If there are some issues, you can reproduce them using the same environment as
the one used by the CI thanks to a docker image, e.g.:

    $ cd [kernel source code]
    $ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
        --pull always mptcp/mptcp-upstream-virtme-docker:latest \
        auto-normal

For more details:

    https://github.com/multipath-tcp/mptcp-upstream-virtme-docker


Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)

Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)