From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v3 00/13] add helpers and vars in mptcp_lib.sh, part 3
Date: Sun, 25 Feb 2024 21:03:48 +0800 [thread overview]
Message-ID: <cover.1708866087.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v3:
- fix shellcheck errors in v2
v2:
- fix shellcheck errors in v1
- print test results with counters
Geliang Tang (13):
selftests: mptcp: capitalize ok/fail/skip
selftests: mptcp: sockopt: print every test result
selftests: mptcp: connect: fix misaligned OK/FAIL
selftests: mptcp: print test results with colors
selftests: mptcp: connect: add dedicated port counter
selftests: mptcp: connect: print out ping tests info
selftests: mptcp: add mptcp_lib_print_test_counter
selftests: mptcp: print test results with counters
selftests: mptcp: move test_fail out of check_expected_one
selftests: mptcp: extract mptcp_lib_check_expected
selftests: mptcp: export event macros in mptcp_lib
selftests: mptcp: add mptcp_lib_verify_listener_events
selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL
tools/testing/selftests/net/mptcp/diag.sh | 18 +-
.../selftests/net/mptcp/mptcp_connect.sh | 87 +++++---
.../testing/selftests/net/mptcp/mptcp_join.sh | 73 +++---
.../testing/selftests/net/mptcp/mptcp_lib.sh | 95 +++++++-
.../selftests/net/mptcp/mptcp_sockopt.sh | 34 ++-
.../testing/selftests/net/mptcp/pm_netlink.sh | 11 +-
.../selftests/net/mptcp/simult_flows.sh | 13 +-
.../selftests/net/mptcp/userspace_pm.sh | 210 +++++++-----------
8 files changed, 297 insertions(+), 244 deletions(-)
--
2.40.1
next reply other threads:[~2024-02-25 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 13:03 Geliang Tang [this message]
2024-02-25 13:03 ` [PATCH mptcp-next v3 01/13] selftests: mptcp: capitalize ok/fail/skip Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 02/13] selftests: mptcp: sockopt: print every test result Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 03/13] selftests: mptcp: connect: fix misaligned OK/FAIL Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 04/13] selftests: mptcp: print test results with colors Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 05/13] selftests: mptcp: connect: add dedicated port counter Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 06/13] selftests: mptcp: connect: print out ping tests info Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 07/13] selftests: mptcp: add mptcp_lib_print_test_counter Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 08/13] selftests: mptcp: print test results with counters Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 09/13] selftests: mptcp: move test_fail out of check_expected_one Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 10/13] selftests: mptcp: extract mptcp_lib_check_expected Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 11/13] selftests: mptcp: export event macros in mptcp_lib Geliang Tang
2024-02-25 13:04 ` [PATCH mptcp-next v3 12/13] selftests: mptcp: add mptcp_lib_verify_listener_events Geliang Tang
2024-02-25 13:04 ` [PATCH mptcp-next v3 13/13] selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL Geliang Tang
2024-02-25 13:51 ` selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL: Tests Results MPTCP CI
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=cover.1708866087.git.tanggeliang@kylinos.cn \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox