From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v8 0/8] mptcp: use GENL_REQ_ATTR_CHECK in userspace pm
Date: Wed, 08 Jan 2025 03:25:03 +0000 [thread overview]
Message-ID: <cc7668c9-d8f1-95b6-10f0-332daef3afd0@gmail.com> (raw)
In-Reply-To: <cover.1736299989.git.tanggeliang@kylinos.cn>
Hi Matthieu,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- KVM Validation: normal: Critical: Global Timeout ❌
- KVM Validation: debug: Success! ✅
- KVM Validation: btf-normal (only bpftest_all): Success! ✅
- KVM Validation: btf-debug (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/12662643252
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/f845d68f8495
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=923191
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)
next prev parent reply other threads:[~2025-01-08 3:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 1:44 [PATCH mptcp-next v8 0/8] mptcp: use GENL_REQ_ATTR_CHECK in userspace pm Geliang Tang
2025-01-08 1:44 ` [PATCH mptcp-next v8 1/8] mptcp: drop info of userspace_pm_remove_id_zero_address Geliang Tang
2025-01-08 1:44 ` [PATCH mptcp-next v8 2/8] mptcp: pm: userspace: flags: clearer msg if no remote addr Geliang Tang
2025-01-08 1:44 ` [PATCH mptcp-next v8 3/8] mptcp: pm: more precise error messages Geliang Tang
2025-01-08 1:44 ` [PATCH mptcp-next v8 4/8] mptcp: pm: improve " Geliang Tang
2025-01-09 15:23 ` Matthieu Baerts
2025-01-08 1:44 ` [PATCH mptcp-next v8 5/8] mptcp: pm: userspace: use GENL_REQ_ATTR_CHECK Geliang Tang
2025-01-09 15:24 ` Matthieu Baerts
2025-01-08 1:44 ` [PATCH mptcp-next v8 6/8] mptcp: pm: remove duplicated error messages Geliang Tang
2025-01-08 1:44 ` [PATCH mptcp-next v8 7/8] mptcp: pm: mark missing address attributes Geliang Tang
2025-01-09 15:24 ` Matthieu Baerts
2025-01-08 1:44 ` [PATCH mptcp-next v8 8/8] mptcp: pm: use NL_SET_ERR_MSG_ATTR when possible Geliang Tang
2025-01-08 3:25 ` MPTCP CI [this message]
2025-01-09 15:23 ` [PATCH mptcp-next v8 0/8] mptcp: use GENL_REQ_ATTR_CHECK in userspace pm Matthieu Baerts
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=cc7668c9-d8f1-95b6-10f0-332daef3afd0@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=matttbe@kernel.org \
--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