From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: Squash to "selftests/bpf: Add bpf_burst scheduler": Tests Results
Date: Wed, 22 Nov 2023 04:49:15 +0000 [thread overview]
Message-ID: <1a241bfb-de8d-3639-10f6-97bb68690425@gmail.com> (raw)
In-Reply-To: <14a1120c9bc792ead2b926208ce85b5f10cb99fd.1700624540.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/4522476651151360
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4522476651151360/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6211326511415296
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6211326511415296/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5648376557993984
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5648376557993984/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5085426604572672
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5085426604572672/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/9712119a0a4b
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-11-22 4:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 3:42 [PATCH mptcp-next] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-11-22 4:49 ` MPTCP CI [this message]
2023-11-27 17:56 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 6:29 [PATCH mptcp-next 9/9] " Geliang Tang
2023-08-15 7:44 ` Squash to "selftests/bpf: Add bpf_burst scheduler": Tests Results MPTCP CI
2023-08-03 4:27 [PATCH mptcp-next v3 6/6] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-08-03 5:31 ` Squash to "selftests/bpf: Add bpf_burst scheduler": Tests Results MPTCP CI
2023-08-02 11:55 [PATCH mptcp-next v2 6/6] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-08-02 13:03 ` Squash to "selftests/bpf: Add bpf_burst scheduler": 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=1a241bfb-de8d-3639-10f6-97bb68690425@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