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 v13 9/9] selftests: mptcp: print test results with colors
Date: Wed, 6 Mar 2024 13:04:25 +0100 [thread overview]
Message-ID: <49dffe4c-4a42-4bbe-ae5d-45c4a80ab2f2@kernel.org> (raw)
In-Reply-To: <3903335eb71697af9348119b569e29c50c9e741d.1709688778.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 06/03/2024 02:40, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> To unify the output formats of all test scripts, this patch adds
> four more helpers:
>
> mptcp_lib_pr_ok()
> mptcp_lib_pr_skip()
> mptcp_lib_pr_fail()
> mptcp_lib_pr_info()
>
> to print out [ OK ], [SKIP], [FAIL] and 'INFO: ' with colors. Use them
> in all scripts to print the "ok/skip/fail/info' using the same 'format'.
>
> Having colors helps to quickly identify issues when looking at a long
> list of output logs and results.
>
> Note that now all print the same keywords, which was not the case
> before, but it is good to uniform that.
(...)
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_lib.sh b/tools/testing/selftests/net/mptcp/mptcp_lib.sh
> index eb740a2f7898..d623c3c418be 100644
> --- a/tools/testing/selftests/net/mptcp/mptcp_lib.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_lib.sh
(...)
> @@ -352,29 +369,30 @@ mptcp_lib_check_tools() {
I think you missed "mptcp_lib_check_output()" just above. Is it OK if I
replace the two 'mptcp_lib_print_err "[FAIL] "' by 'mptcp_lib_pr_fail'
when applying the series?
(...)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-03-06 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 1:40 [PATCH mptcp-next v13 0/9] add helpers and vars in mptcp_lib.sh, part 3 Geliang Tang
2024-03-06 1:40 ` [PATCH mptcp-next v13 1/9] selftests: mptcp: print all error messages to stdout Geliang Tang
2024-03-06 1:40 ` [PATCH mptcp-next v13 2/9] selftests: mptcp: connect: add dedicated port counter Geliang Tang
2024-03-06 12:02 ` Matthieu Baerts
2024-03-06 1:40 ` [PATCH mptcp-next v13 3/9] selftests: mptcp: connect: fix misaligned output Geliang Tang
2024-03-06 1:40 ` [PATCH mptcp-next v13 4/9] selftests: mptcp: sockopt: print every test result Geliang Tang
2024-03-06 1:40 ` [PATCH mptcp-next v13 5/9] selftests: mptcp: export TEST_COUNTER variable Geliang Tang
2024-03-06 1:40 ` [PATCH mptcp-next v13 6/9] selftests: mptcp: add print_title in mptcp_lib Geliang Tang
2024-03-06 1:40 ` [PATCH mptcp-next v13 7/9] selftests: mptcp: print test results with counters Geliang Tang
2024-03-06 12:04 ` Matthieu Baerts
2024-03-06 1:40 ` [PATCH mptcp-next v13 8/9] selftests: mptcp: connect: use += operator to append strings Geliang Tang
2024-03-06 1:40 ` [PATCH mptcp-next v13 9/9] selftests: mptcp: print test results with colors Geliang Tang
2024-03-06 2:33 ` selftests: mptcp: print test results with colors: Tests Results MPTCP CI
2024-03-06 2:49 ` MPTCP CI
2024-03-06 12:04 ` Matthieu Baerts [this message]
2024-03-06 12:01 ` [PATCH mptcp-next v13 0/9] add helpers and vars in mptcp_lib.sh, part 3 Matthieu Baerts
2024-03-06 15:28 ` 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=49dffe4c-4a42-4bbe-ae5d-45c4a80ab2f2@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.