From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Davide Caratti <dcaratti@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: don't account accept() of non-MPC client as fallback to TCP: Tests Results
Date: Tue, 05 Mar 2024 15:20:56 +0000 [thread overview]
Message-ID: <1b5d0fb6-0755-5a0e-bd5c-15a0f1fabfd3@gmail.com> (raw)
In-Reply-To: <cf0fb6eb68466bef37d685cc8a52cad3b69c4e7a.1709647631.git.dcaratti@redhat.com>
Hi Davide,
Thank you for your modifications, that's great!
Our CI (Cirrus) did some validations with a debug kernel and here is its report:
- KVM Validation: debug (except selftest_mptcp_join):
- Unstable: 1 failed test(s): packetdrill_sockopts 🔴:
- Task: https://cirrus-ci.com/task/5651700250312704
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5651700250312704/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5088750296891392
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5088750296891392/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/e08e8f186d4d
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 (NGI0 Core)
next prev parent reply other threads:[~2024-03-05 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 14:07 [PATCH mptcp-next] mptcp: don't account accept() of non-MPC client as fallback to TCP Davide Caratti
2024-03-05 14:59 ` mptcp: don't account accept() of non-MPC client as fallback to TCP: Tests Results MPTCP CI
2024-03-05 15:20 ` MPTCP CI [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-05 15:19 [PATCH mptcp-net v2] mptcp: don't account accept() of non-MPC client as fallback to TCP Davide Caratti
2024-03-05 16:12 ` mptcp: don't account accept() of non-MPC client as fallback to TCP: Tests Results MPTCP CI
2024-03-05 16:32 ` 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=1b5d0fb6-0755-5a0e-bd5c-15a0f1fabfd3@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=dcaratti@redhat.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).