From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: userspace pm get addr tests: Tests Results
Date: Wed, 14 Feb 2024 12:37:14 +0000 [thread overview]
Message-ID: <6335189f-669f-9503-28ad-574a79be405b@gmail.com> (raw)
In-Reply-To: <b46824466aa1ede15dd8c8e0e5d6233b8b85ddfb.1707910454.git.tanggeliang@kylinos.cn>
Hi Geliang,
Thank you for your modifications, that's great!
Our CI (GitHub Action) did some validations and here is its report:
- KVM Validation: normal:
- Success! ✅:
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/7900781714
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/ef0e97c755ed
If there are some issues, you can reproduce them using the same environment as
the one used by the CI thanks to a docker image, e.g.:
$ cd [kernel source code]
$ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
--pull always mptcp/mptcp-upstream-virtme-docker:latest \
auto-normal
For more details:
https://github.com/multipath-tcp/mptcp-upstream-virtme-docker
Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)
Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)
next prev parent reply other threads:[~2024-02-14 12:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 11:39 [PATCH mptcp-next v12 00/15] dump for userspace pm Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 01/15] mptcp: export mptcp_genl_family & mptcp_nl_fill_addr Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 02/15] mptcp: implement mptcp_userspace_pm_dump_addr Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 03/15] mptcp: add token for get-addr in yaml Geliang Tang
2024-02-15 23:00 ` Mat Martineau
2024-02-14 11:39 ` [PATCH mptcp-next v12 04/15] mptcp: dump addrs in userspace pm list Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 05/15] mptcp: check userspace pm flags Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 06/15] selftests: mptcp: add userspace pm subflow flag Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 07/15] selftests: mptcp: add token for dump_addr Geliang Tang
2024-02-14 11:39 ` [PATCH mptcp-next v12 08/15] selftests: mptcp: add check_output helper Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 09/15] selftests: mptcp: dump after creating id 0 subflow Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 10/15] selftests: mptcp: dump userspace addrs list Geliang Tang
2024-02-15 22:57 ` Mat Martineau
2024-02-16 10:30 ` Matthieu Baerts
2024-02-14 11:40 ` [PATCH mptcp-next v12 11/15] mptcp: add userspace_pm_lookup_addr_by_id helper Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 12/15] mptcp: implement mptcp_userspace_pm_get_addr Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 13/15] mptcp: get addr in userspace pm list Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 14/15] selftests: mptcp: add token for get_addr Geliang Tang
2024-02-14 11:40 ` [PATCH mptcp-next v12 15/15] selftests: mptcp: userspace pm get addr tests Geliang Tang
2024-02-14 12:37 ` MPTCP CI [this message]
2024-02-14 12:48 ` selftests: mptcp: userspace pm get addr tests: Tests Results MPTCP CI
-- strict thread matches above, loose matches on Subject: below --
2024-02-20 9:58 [PATCH mptcp-next v14 14/14] selftests: mptcp: userspace pm get addr tests Geliang Tang
2024-02-20 10:51 ` selftests: mptcp: userspace pm get addr tests: Tests Results MPTCP CI
2024-02-20 18:27 ` MPTCP CI
2024-02-20 18:46 ` MPTCP CI
2024-02-16 7:42 [PATCH mptcp-next v13 14/14] selftests: mptcp: userspace pm get addr tests Geliang Tang
2024-02-16 8:34 ` selftests: mptcp: userspace pm get addr tests: Tests Results MPTCP CI
2024-02-16 9:55 ` MPTCP CI
2024-02-16 10:14 ` MPTCP CI
2024-02-16 10:24 ` Matthieu Baerts
2024-02-16 11:08 ` MPTCP CI
2024-02-16 11:31 ` MPTCP CI
2024-02-16 20:33 ` MPTCP CI
2023-12-19 8:19 [PATCH mptcp-next v3 14/14] selftests: mptcp: userspace pm get addr tests Geliang Tang
2023-12-19 8:36 ` selftests: mptcp: userspace pm get addr tests: Tests Results MPTCP CI
2023-12-19 10:55 ` MPTCP CI
2023-12-19 12:19 ` Matthieu Baerts
2023-12-18 9:23 [PATCH mptcp-next v2 15/15] selftests: mptcp: userspace pm get addr tests Geliang Tang
2023-12-18 10:58 ` selftests: mptcp: userspace pm get addr tests: Tests Results MPTCP CI
2023-12-11 8:15 [PATCH mptcp-next 12/12] selftests: mptcp: userspace pm get addr tests Geliang Tang
2023-12-11 11:24 ` selftests: mptcp: userspace pm get addr tests: 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=6335189f-669f-9503-28ad-574a79be405b@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--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