From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: userspace pm send RM_ADDR for ID 0: Tests Results
Date: Tue, 17 Oct 2023 04:08:38 +0000 [thread overview]
Message-ID: <dd43ecbb-0915-fb87-4013-8ae173d3f8a7@gmail.com> (raw)
In-Reply-To: <d85a4f247289d84da2c6a8235afc46fa144a91e7.1697511436.git.geliang.tang@suse.com>
Hi Geliang,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- KVM Validation: normal (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6363765940158464
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6363765940158464/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/4956391056605184
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4956391056605184/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5519341010026496
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5519341010026496/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6082290963447808
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6082290963447808/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/32eeb039f540
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-debug
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 (Tessares)
next prev parent reply other threads:[~2023-10-17 4:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 3:00 [PATCH mptcp-next v17 0/9] userspace pm remove id 0 subflow & address Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 1/9] selftests: mptcp: run userspace pm tests slower Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 2/9] selftests: mptcp: fix wait_rm_addr/sf parameters Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 3/9] Squash to "selftests: mptcp: userspace pm create id 0 subflow" Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 4/9] Squash to "mptcp: add mptcpi_subflows_total counter" Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 5/9] Squash to "selftests: mptcp: add chk_subflows_total helper" Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 6/9] selftests: mptcp: userspace pm remove initial subflow Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 7/9] mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 8/9] mptcp: userspace pm rename remove_err to out Geliang Tang
2023-10-17 3:00 ` [PATCH mptcp-next v17 9/9] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-17 4:08 ` MPTCP CI [this message]
2023-10-22 23:06 ` [PATCH mptcp-next v17 0/9] userspace pm remove id 0 subflow & address Matthieu Baerts
2023-10-22 23:16 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2023-10-13 5:46 [PATCH mptcp-next v16 8/8] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-13 6:57 ` selftests: mptcp: userspace pm send RM_ADDR for ID 0: Tests Results MPTCP CI
2023-10-13 10:18 ` MPTCP CI
2023-10-12 8:52 [PATCH mptcp-next v15 7/7] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-12 10:09 ` selftests: mptcp: userspace pm send RM_ADDR for ID 0: Tests Results MPTCP CI
2023-10-11 13:35 [PATCH mptcp-next v14 7/7] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-11 14:46 ` selftests: mptcp: userspace pm send RM_ADDR for ID 0: Tests Results MPTCP CI
2023-10-11 15:37 ` MPTCP CI
2023-10-11 9:50 [PATCH mptcp-next v13 5/5] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-11 10:58 ` selftests: mptcp: userspace pm send RM_ADDR for ID 0: Tests Results MPTCP CI
2023-10-09 6:03 [PATCH mptcp-next v12 5/5] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-09 7:05 ` selftests: mptcp: userspace pm send RM_ADDR for ID 0: 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=dd43ecbb-0915-fb87-4013-8ae173d3f8a7@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
/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