From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests/bpf: Add mptcpify selftest: Tests Results
Date: Sat, 01 Jul 2023 14:02:33 +0000 [thread overview]
Message-ID: <01906f98-2d8c-8115-7c68-e486e77669a9@gmail.com> (raw)
In-Reply-To: <56db1c21d35a76ebc9cc6017da64b30add33304e.1688215769.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/6011347134054400
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6011347134054400/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6574297087475712
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6574297087475712/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/4744709738856448
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4744709738856448/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
- Task: https://cirrus-ci.com/task/5448397180633088
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5448397180633088/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/c3be2bbd7a11
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-07-01 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 12:56 [PATCH mptcp-next v2 0/4] BPF 'force to MPTCP' Geliang Tang
2023-07-01 12:56 ` [PATCH mptcp-next v2 1/4] Squash to "selftests/bpf: add two mptcp netns helpers" Geliang Tang
2023-07-01 12:56 ` [PATCH mptcp-next v2 2/4] bpf: Add bpf_mptcpify helper Geliang Tang
2023-07-01 15:32 ` kernel test robot
2023-07-01 16:55 ` kernel test robot
2023-07-01 12:56 ` [PATCH mptcp-next v2 3/4] selftests/bpf: Test " Geliang Tang
2023-07-01 12:57 ` [PATCH mptcp-next v2 4/4] selftests/bpf: Add mptcpify selftest Geliang Tang
2023-07-01 14:02 ` MPTCP CI [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-05 6:56 [PATCH mptcp-next v4 7/7] " Geliang Tang
2023-07-05 8:15 ` selftests/bpf: Add mptcpify selftest: Tests Results MPTCP CI
2023-07-03 6:40 [PATCH mptcp-next v3 5/5] selftests/bpf: Add mptcpify selftest Geliang Tang
2023-07-03 7:52 ` selftests/bpf: Add mptcpify selftest: Tests Results MPTCP CI
2023-06-29 2:12 [PATCH mptcp-next 4/4] selftests/bpf: Add mptcpify selftest Geliang Tang
2023-06-29 18:16 ` selftests/bpf: Add mptcpify selftest: Tests Results MPTCP CI
2023-06-29 20:32 ` 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=01906f98-2d8c-8115-7c68-e486e77669a9@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