From: Geliang Tang <geliang@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net 1/5] selftests: mptcp: simult flows: fix some subtest names
Date: Tue, 13 Feb 2024 19:34:59 +0800 [thread overview]
Message-ID: <ZctT4/w/nH6+4Ocz@t480> (raw)
In-Reply-To: <20240209-selftests-mptcp-uniq-title-v1-1-e4fb3a3b5f66@kernel.org>
Hi Matt,
On Fri, Feb 09, 2024 at 06:28:39PM +0100, Matthieu Baerts (NGI0) wrote:
> The selftest was correctly recording all the results, but the 'reverse
> direction' part was missing in the name when needed.
>
> It is important to have a unique (sub)test name in TAP, because some CI
> environments drop tests with duplicated name.
>
> Fixes: 675d99338e7a ("selftests: mptcp: simult flows: format subtests results in TAP")
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> ---
> tools/testing/selftests/net/mptcp/simult_flows.sh | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/net/mptcp/simult_flows.sh b/tools/testing/selftests/net/mptcp/simult_flows.sh
> index 619be0e1acf5..f377ef01970b 100755
> --- a/tools/testing/selftests/net/mptcp/simult_flows.sh
> +++ b/tools/testing/selftests/net/mptcp/simult_flows.sh
> @@ -250,7 +250,8 @@ run_test()
> [ $bail -eq 0 ] || exit $ret
> fi
>
> - printf "%-60s" "$msg - reverse direction"
> + msg="${msg} - reverse direction"
How about using '+=' operator to append a string like:
msg+=" - reverse direction"
The same in patch 3 and patch 4:
msg+=" after flush"
WDYT?
Thanks,
-Geliang
> + printf "%-60s" "${msg}"
> do_transfer $large $small $time
> lret=$?
> mptcp_lib_result_code "${lret}" "${msg}"
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-02-13 11:35 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 [this message]
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
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=ZctT4/w/nH6+4Ocz@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