From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v11 0/8] add helpers and vars in mptcp_lib.sh, part 3
Date: Sun, 3 Mar 2024 19:52:49 +0800 [thread overview]
Message-ID: <cover.1709466624.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v11:
- fix the shellcheck error in v10
v10:
- split two more patches (#4 and #5) from #6 and #7
- update commit logs
v9:
- move print_larger_title from patch 5 to patch 2
- move MPTCP_LIB_TEST_FORMAT to a more suitable location in patch 4 and
patch 5
v8:
- address every comment from Matt in v7.
v7:
- address every comment from Matt in v6.
v6:
- only include the first 7 patches in v5
- add mptcp_lib_pr_* helpers
- add print_title helpers
- align the output of simult_flows.sh
v5:
- don't use mptcp_lib_print_test_counter in mptcp_join.sh, it breaks
skip_test().
v4:
- set test_cnt to 0, use ++counter in mptcp_lib_print_test_counter() to
fix the following mismatched test counters:
# 012 userspace pm server fullmesh
# syn [ OK ]
# synack [ OK ]
# ack [ OK ]
# add [ OK ]
# echo [FAIL] got 1 ADD_ADDR echo[s] expected 2
# Server ns stats
# TcpPassiveOpens 5 0.0
# TcpInSegs 25 0.0
... ...
#
# 1 failure(s) has(ve) been detected:
# - 13: userspace pm server fullmesh
v3:
- fix shellcheck errors in v2
v2:
- fix shellcheck errors in v1
- print test results with counters
Geliang Tang (8):
selftests: mptcp: print all error messages to stdout
selftests: mptcp: connect: add dedicated port counter
selftests: mptcp: connect: fix misaligned output
selftests: mptcp: sockopt: print every test result
selftests: mptcp: export TEST_COUNTER variable
selftests: mptcp: add print_title in mptcp_lib
selftests: mptcp: print test results with counters
selftests: mptcp: print test results with colors
tools/testing/selftests/net/mptcp/diag.sh | 19 ++---
.../selftests/net/mptcp/mptcp_connect.sh | 76 ++++++++++---------
.../testing/selftests/net/mptcp/mptcp_join.sh | 28 +++----
.../testing/selftests/net/mptcp/mptcp_lib.sh | 45 ++++++++---
.../selftests/net/mptcp/mptcp_sockopt.sh | 33 ++++----
.../testing/selftests/net/mptcp/pm_netlink.sh | 5 +-
.../selftests/net/mptcp/simult_flows.sh | 14 ++--
.../selftests/net/mptcp/userspace_pm.sh | 22 ++----
8 files changed, 131 insertions(+), 111 deletions(-)
--
2.40.1
next reply other threads:[~2024-03-03 11:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 11:52 Geliang Tang [this message]
2024-03-03 11:52 ` [PATCH mptcp-next v11 1/8] selftests: mptcp: print all error messages to stdout Geliang Tang
2024-03-04 12:31 ` Matthieu Baerts
2024-03-03 11:52 ` [PATCH mptcp-next v11 2/8] selftests: mptcp: connect: add dedicated port counter Geliang Tang
2024-03-04 12:31 ` Matthieu Baerts
2024-03-03 11:52 ` [PATCH mptcp-next v11 3/8] selftests: mptcp: connect: fix misaligned output Geliang Tang
2024-03-03 11:52 ` [PATCH mptcp-next v11 4/8] selftests: mptcp: sockopt: print every test result Geliang Tang
2024-03-04 12:32 ` Matthieu Baerts
2024-03-03 11:52 ` [PATCH mptcp-next v11 5/8] selftests: mptcp: export TEST_COUNTER variable Geliang Tang
2024-03-03 11:52 ` [PATCH mptcp-next v11 6/8] selftests: mptcp: add print_title in mptcp_lib Geliang Tang
2024-03-03 11:52 ` [PATCH mptcp-next v11 7/8] selftests: mptcp: print test results with counters Geliang Tang
2024-03-03 11:52 ` [PATCH mptcp-next v11 8/8] selftests: mptcp: print test results with colors Geliang Tang
2024-03-03 12:40 ` selftests: mptcp: print test results with colors: Tests Results MPTCP CI
2024-03-03 13:00 ` MPTCP CI
2024-03-04 12:32 ` [PATCH mptcp-next v11 8/8] selftests: mptcp: print test results with colors Matthieu Baerts
2024-03-04 12:31 ` [PATCH mptcp-next v11 0/8] add helpers and vars in mptcp_lib.sh, part 3 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=cover.1709466624.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).