From: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Subject: [PATCH mptcp-net 0/2] Fixes for "selftests: mptcp: connect: cover alt modes"
Date: Tue, 15 Jul 2025 11:49:07 +0200 [thread overview]
Message-ID: <20250715-selftests-mptcp-connect-modes-fixes-v1-0-58fc475d9397@kernel.org> (raw)
Without that, all mptcp_connect*.sh subtests have the same name, e.g.
mptcp_connect: ping tests ## from mptcp_connect.sh
mptcp_connect: ping tests ## from mptcp_connect_checksum.sh
mptcp_connect: ping tests ## from mptcp_connect_mmap.sh
mptcp_connect: ping tests ## from mptcp_connect_sendfile.sh
In such case, the CI will only see one subtest, not 4 different ones.
To fix that, MPTCP_LIB_KSFT_TEST env var can simply be set.
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Matthieu Baerts (NGI0) (2):
Squash to "selftests: mptcp: connect: also cover alt modes"
Squash to "selftests: mptcp: connect: also cover checksum"
tools/testing/selftests/net/mptcp/mptcp_connect_checksum.sh | 3 ++-
tools/testing/selftests/net/mptcp/mptcp_connect_mmap.sh | 3 ++-
tools/testing/selftests/net/mptcp/mptcp_connect_sendfile.sh | 3 ++-
3 files changed, 6 insertions(+), 3 deletions(-)
---
base-commit: 422cf93634436650f6ea5dacb37f1edfed7ab3c9
change-id: 20250715-selftests-mptcp-connect-modes-fixes-61383574b42a
Best regards,
--
Matthieu Baerts (NGI0) <matttbe@kernel.org>
next reply other threads:[~2025-07-15 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 9:49 Matthieu Baerts (NGI0) [this message]
2025-07-15 9:49 ` [PATCH mptcp-net 1/2] Squash to "selftests: mptcp: connect: also cover alt modes" Matthieu Baerts (NGI0)
2025-07-15 9:49 ` [PATCH mptcp-net 2/2] Squash to "selftests: mptcp: connect: also cover checksum" Matthieu Baerts (NGI0)
2025-07-15 9:52 ` [PATCH mptcp-net 0/2] Fixes for "selftests: mptcp: connect: cover alt modes" Geliang Tang
2025-07-15 17:03 ` Matthieu Baerts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250715-selftests-mptcp-connect-modes-fixes-v1-0-58fc475d9397@kernel.org \
--to=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).