From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v7 6/8] selftests: mptcp: add test counter helpers
Date: Thu, 29 Feb 2024 13:28:38 +0100 [thread overview]
Message-ID: <4930a445-3a30-4272-aa26-4dbff29b0c15@kernel.org> (raw)
In-Reply-To: <fea0084f-665b-4ea2-96cd-f9c025c02a28@kernel.org>
On 29/02/2024 12:58, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 29/02/2024 10:51, Geliang Tang wrote:
>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>
>> This patch adds two vars in mptcp_lib.sh, MPTCP_LIB_TEST_COUNTER for
>> the test counter and MPTCP_LIB_TEST_FORMAT for the test print format.
>> Also add two helpers, mptcp_lib_inc_test_counter(), increase the test
>> counter, and mptcp_lib_pr_title_counter(), print the test title with
>> counter. They are used in mptcp_join.sh first.
>
> Please add the reason, something like: Each MPTCP selftest is having
> subtests, and it helps to give them a number to quickly identify them.
> This can be managed by mptcp_lib.sh, reusing what has been done here.
> The following commit will use these new helpers in the other tests.
>
>> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
>> ---
(...)
>> +mptcp_lib_pr_title_counter() {
>> + : "${MPTCP_LIB_TEST_COUNTER:?}"
>> + : "${MPTCP_LIB_TEST_FORMAT:="%02u %-50s"}"
>> +
>> + printf "${MPTCP_LIB_TEST_FORMAT}" "${MPTCP_LIB_TEST_COUNTER}" "${*}"
>
> I didn't check: can you not print the title and increment the counter
> (via mptcp_lib_inc_test_counter) from here? I think that would be a good
> practice to do that instead of having to deal with the counter in
> different places.
>
> We would only call "mptcp_lib_inc_test_counter()" from other scripts
> when a test is skipped.
OK, I just saw you added mptcp_lib_print_title() in the next patch. Why
did you not use it for mptcp_join.sh?
Can you not call "mptcp_lib_inc_test_counter" in the "if skip_test" from
mptcp_join.sh and use mptcp_lib_print_title()? (if you do that, I guess
we don't need mptcp_lib_pr_title_counter(), no?)
>
>> +}
>
> Cheers,
> Matt
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-02-29 12:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 9:51 [PATCH mptcp-next v7 0/8] add helpers and vars in mptcp_lib.sh, part 3 Geliang Tang
2024-02-29 9:51 ` [PATCH mptcp-net v7 1/8] selftests: mptcp: diag: return KSFT_FAIL not test_cnt Geliang Tang
2024-02-29 10:51 ` Matthieu Baerts
2024-02-29 9:51 ` [PATCH mptcp-next v7 2/8] selftests: mptcp: connect: add dedicated port counter Geliang Tang
2024-02-29 11:23 ` Matthieu Baerts
2024-02-29 12:18 ` Geliang Tang
2024-02-29 12:22 ` Matthieu Baerts
2024-03-01 7:01 ` Geliang Tang
2024-02-29 9:51 ` [PATCH mptcp-next v7 3/8] selftests: mptcp: connect: fix misaligned output Geliang Tang
2024-02-29 9:51 ` [PATCH mptcp-next v7 4/8] selftests: mptcp: simult_flows: " Geliang Tang
2024-02-29 10:07 ` Geliang Tang
2024-02-29 10:27 ` Matthieu Baerts
2024-02-29 12:01 ` Geliang Tang
2024-02-29 12:18 ` Matthieu Baerts
2024-02-29 14:35 ` Matthieu Baerts
2024-02-29 9:51 ` [PATCH mptcp-next v7 5/8] selftests: mptcp: sockopt: unify ipv4/ipv6 as v4/v6 Geliang Tang
2024-02-29 11:31 ` Matthieu Baerts
2024-02-29 12:08 ` Geliang Tang
2024-02-29 12:20 ` Matthieu Baerts
2024-02-29 9:51 ` [PATCH mptcp-next v7 6/8] selftests: mptcp: add test counter helpers Geliang Tang
2024-02-29 11:58 ` Matthieu Baerts
2024-02-29 12:03 ` Matthieu Baerts
2024-02-29 12:28 ` Matthieu Baerts [this message]
2024-03-01 7:03 ` Geliang Tang
2024-02-29 9:51 ` [PATCH mptcp-next v7 7/8] selftests: mptcp: print test results with counters Geliang Tang
2024-02-29 12:44 ` Matthieu Baerts
2024-02-29 9:51 ` [PATCH mptcp-next v7 8/8] selftests: mptcp: print test results with colors Geliang Tang
2024-02-29 10:43 ` selftests: mptcp: print test results with colors: Tests Results MPTCP CI
2024-02-29 13:04 ` [PATCH mptcp-next v7 8/8] selftests: mptcp: print test results with colors Matthieu Baerts
2024-03-01 7:16 ` Geliang Tang
2024-03-04 11:12 ` 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=4930a445-3a30-4272-aa26-4dbff29b0c15@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.