From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v8 0/7] implement mptcp read_sock
Date: Wed, 09 Jul 2025 16:06:42 +0000 [thread overview]
Message-ID: <69005cec-14cb-451c-e117-a25a25f09b69@gmail.com> (raw)
In-Reply-To: <cover.1752045499.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: Critical: 223 Call Trace(s) - Critical: Global Timeout ❌
- 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/16172161051
Initiator: Matthieu Baerts (NGI0)
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/aa295276bd34
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=980362
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-07-09 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 7:25 [PATCH mptcp-next v8 0/7] implement mptcp read_sock Geliang Tang
2025-07-09 7:25 ` [PATCH mptcp-next v8 1/7] mptcp: add eat_recv_skb helper Geliang Tang
2025-07-09 7:25 ` [PATCH mptcp-next v8 2/7] mptcp: implement .read_sock Geliang Tang
2025-07-09 7:25 ` [PATCH mptcp-next v8 3/7] tcp: export tcp_splice_state Geliang Tang
2025-07-09 7:25 ` [PATCH mptcp-next v8 4/7] mptcp: add recv_should_stop helper Geliang Tang
2025-07-09 7:25 ` [PATCH mptcp-next v8 5/7] mptcp: implement .splice_read Geliang Tang
2025-07-09 7:25 ` [PATCH mptcp-next v8 6/7] selftests: mptcp: add splice io mode Geliang Tang
2025-07-09 7:25 ` [PATCH mptcp-next v8 7/7] selftests: mptcp: connect: cover splice mode Geliang Tang
2025-07-09 16:06 ` MPTCP CI [this message]
2025-07-09 17:53 ` [PATCH mptcp-next v8 0/7] implement mptcp read_sock 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=69005cec-14cb-451c-e117-a25a25f09b69@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.