From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH bpf-next 00/14] use start_server and connect_to helpers
Date: Wed, 10 Apr 2024 17:52:54 +0000 [thread overview]
Message-ID: <d521c25b-d25a-1286-2e10-4ec3aadc91b9@gmail.com> (raw)
In-Reply-To: <cover.1712733999.git.tanggeliang@kylinos.cn>
Hi Geliang,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- KVM Validation: normal: Success! ✅
- KVM Validation: debug: Success! ✅
- KVM Validation: btf (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/8635157069
Initiator: Matthieu Baerts (NGI0)
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/338146465227
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=843118
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)
prev parent reply other threads:[~2024-04-10 17:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 7:29 [PATCH bpf-next 00/14] use start_server and connect_to helpers Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 01/14] selftests/bpf: Add start_server_addr helper Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 02/14] selftests/bpf: Use start_server_addr in cls_redirect Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 03/14] selftests/bpf: Use connect_to_addr " Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 04/14] selftests/bpf: Use start_server_addr in sk_assign Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 05/14] selftests/bpf: Use connect_to_addr " Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 06/14] selftests/bpf: Use log_err in network_helpers Geliang Tang
2024-04-10 8:14 ` Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 07/14] selftests/bpf: Use start_server_addr in test_sock_addr Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 08/14] selftests/bpf: Use connect_to_addr " Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 09/14] selftests/bpf: Add function pointer for __start_server Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 10/14] selftests/bpf: Add start_server_setsockopt helper Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 11/14] selftests/bpf: Use start_server_setsockopt in sockopt_inherit Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 12/14] selftests/bpf: Use connect_to_fd " Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 13/14] selftests/bpf: Use start_server_* in test_tcp_check_syncookie Geliang Tang
2024-04-10 7:29 ` [PATCH bpf-next 14/14] selftests/bpf: Use connect_to_addr " Geliang Tang
2024-04-10 17:52 ` MPTCP CI [this message]
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=d521c25b-d25a-1286-2e10-4ec3aadc91b9@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).