From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Jason Xing <kernelxing@tencent.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH net-next RESEND v6 0/7] Implement reset reason mechanism to detect
Date: Thu, 18 Apr 2024 14:31:03 +0000 [thread overview]
Message-ID: <61d1f35a-617e-6cb1-0cb5-3b9814db08bb@gmail.com> (raw)
In-Reply-To: <20240418133248.56378-1-kerneljasonxing@gmail.com>
Hi Jason,
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/8739169189
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/2e5b93dff34e
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=845801
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-18 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 13:32 [PATCH net-next RESEND v6 0/7] Implement reset reason mechanism to detect Jason Xing
2024-04-18 13:32 ` [PATCH net-next v6 1/7] net: introduce rstreason to detect why the RST is sent Jason Xing
2024-04-18 13:32 ` [PATCH net-next v6 2/7] rstreason: prepare for passive reset Jason Xing
2024-04-18 13:32 ` [PATCH net-next v6 3/7] rstreason: prepare for active reset Jason Xing
2024-04-18 13:32 ` [PATCH net-next v6 4/7] tcp: support rstreason for passive reset Jason Xing
2024-04-18 13:32 ` [PATCH net-next v6 5/7] mptcp: " Jason Xing
2024-04-18 13:32 ` [PATCH net-next v6 6/7] mptcp: introducing a helper into active reset logic Jason Xing
2024-04-18 13:32 ` [PATCH net-next v6 7/7] rstreason: make it work in trace world Jason Xing
2024-04-18 14:31 ` 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=61d1f35a-617e-6cb1-0cb5-3b9814db08bb@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=kernelxing@tencent.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).