From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: remove id 0 subflow & address: Tests Results
Date: Thu, 17 Aug 2023 15:27:08 +0000 [thread overview]
Message-ID: <e688e440-ea61-3dd2-87ef-fe4982f6907e@gmail.com> (raw)
In-Reply-To: <4d399e6564e6a4c2ea3fda6f6f4f7ca50dd6c0ac.1692281317.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/5698108105949184
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5698108105949184/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/4853683175817216
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4853683175817216/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5135158152527872
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5135158152527872/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6261058059370496
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6261058059370496/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/131df8187f2c
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-08-17 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 14:10 [PATCH mptcp-next v3 0/3] userspace pm remove id 0 subflow & address Geliang Tang
2023-08-17 14:10 ` [PATCH mptcp-next v3 1/3] mptcp: allow creating id 0 subflow Geliang Tang
2023-08-17 14:10 ` [PATCH mptcp-next v3 2/3] mptcp: remove id 0 address Geliang Tang
2023-08-17 16:32 ` Matthieu Baerts
2023-08-17 14:10 ` [PATCH mptcp-next v3 3/3] selftests: mptcp: remove id 0 subflow & address Geliang Tang
2023-08-17 15:27 ` MPTCP CI [this message]
2023-08-17 16:37 ` Matthieu Baerts
2023-08-17 16:30 ` [PATCH mptcp-next v3 0/3] userspace pm " Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 7:06 [PATCH mptcp-next v2 4/4] selftests: mptcp: " Geliang Tang
2023-08-09 8:35 ` selftests: mptcp: remove id 0 subflow & address: Tests Results MPTCP CI
2023-08-08 5:38 [PATCH mptcp-next 4/4] selftests: mptcp: remove id 0 subflow & address Geliang Tang
2023-08-08 7:15 ` selftests: mptcp: remove id 0 subflow & address: 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=e688e440-ea61-3dd2-87ef-fe4982f6907e@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