From: Geliang Tang <geliang@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net 0/5] selftests: mptcp: unique subtest names
Date: Tue, 13 Feb 2024 23:30:39 +0800 [thread overview]
Message-ID: <ZcuLHz0O+kl0PZY1@t480> (raw)
In-Reply-To: <20240209-selftests-mptcp-uniq-title-v1-0-e4fb3a3b5f66@kernel.org>
On Fri, Feb 09, 2024 at 06:28:38PM +0100, Matthieu Baerts (NGI0) wrote:
> It is important to have a unique (sub)test name in TAP, because some CI
> environments drop tests with duplicated name.
>
> When working on adding subtests support in Netdev's NIPA CI, I found out
> some subtests had the same name. The name is used as a key, it should
> then be unique, otherwise we don't track duplicated tests.
>
> The fixes have been split in different patches, because it fixes
> different commits. But the idea is always the same: make sure subtest
> names are unique.
>
> The last patch is not for -net, that's a new feature to make sure we
> don't add duplicated names later.
>
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> ---
> Matthieu Baerts (NGI0) (5):
> selftests: mptcp: simult flows: fix some subtest names
> selftests: mptcp: userspace_pm: unique subtest names
> selftests: mptcp: diag: unique 'in use' subtest names
> selftests: mptcp: diag: unique 'cestab' subtest names
> selftests: mptcp: lib: catch duplicated subtest entries
LGTM!
Reviewed-by: Geliang Tang <geliang@kernel.org>
Thanks,
-Geliang
>
> tools/testing/selftests/net/mptcp/diag.sh | 37 ++++++++++++++---------
> tools/testing/selftests/net/mptcp/mptcp_lib.sh | 21 +++++++++++++
> tools/testing/selftests/net/mptcp/simult_flows.sh | 3 +-
> tools/testing/selftests/net/mptcp/userspace_pm.sh | 4 +--
> 4 files changed, 48 insertions(+), 17 deletions(-)
> ---
> base-commit: 0c8d1475f726a95cddb393e45f0b4d8ec0e15785
> change-id: 20240209-selftests-mptcp-uniq-title-2e2df0c17695
>
> Best regards,
> --
> Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
prev parent reply other threads:[~2024-02-13 15:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 17:28 [PATCH mptcp-net 0/5] selftests: mptcp: unique subtest names Matthieu Baerts (NGI0)
2024-02-09 17:28 ` [PATCH mptcp-net 1/5] selftests: mptcp: simult flows: fix some " Matthieu Baerts (NGI0)
2024-02-13 11:34 ` Geliang Tang
2024-02-13 12:06 ` Matthieu Baerts
2024-02-13 13:48 ` Geliang Tang
2024-02-13 15:21 ` Matthieu Baerts
2024-02-09 17:28 ` [PATCH mptcp-net 2/5] selftests: mptcp: userspace_pm: unique " Matthieu Baerts (NGI0)
2024-02-09 17:28 ` [PATCH mptcp-net 3/5] selftests: mptcp: diag: unique 'in use' " Matthieu Baerts (NGI0)
2024-02-09 17:28 ` [PATCH mptcp-net 4/5] selftests: mptcp: diag: unique 'cestab' " Matthieu Baerts (NGI0)
2024-02-09 17:28 ` [PATCH mptcp-net 5/5] selftests: mptcp: lib: catch duplicated subtest entries Matthieu Baerts (NGI0)
2024-02-09 18:19 ` selftests: mptcp: lib: catch duplicated subtest entries: Tests Results MPTCP CI
2024-02-09 20:46 ` MPTCP CI
2024-02-13 14:28 ` MPTCP CI
2024-02-13 15:53 ` MPTCP CI
2024-02-13 4:21 ` [PATCH mptcp-net 0/5] selftests: mptcp: unique subtest names Geliang Tang
2024-02-13 11:57 ` Matthieu Baerts
2024-02-13 15:30 ` Geliang Tang [this message]
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=ZcuLHz0O+kl0PZY1@t480 \
--to=geliang@kernel.org \
--cc=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