From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2 0/7] BPF path manager, part 3
Date: Wed, 15 Jan 2025 10:25:24 +0100 [thread overview]
Message-ID: <c8b97326-8cd8-402a-932a-8a0b013eeafa@kernel.org> (raw)
In-Reply-To: <1efe02ff-3c0e-7a2c-8e80-bee3eec54d68@gmail.com>
Hi Geliang,
On 15/01/2025 09:13, MPTCP CI wrote:
> Hi Geliang,
>
> Thank you for your modifications, that's great!
>
> Our CI did some validations and here is its report:
>
> - KVM Validation: normal: Unstable: 1 failed test(s): selftest_mptcp_join 🔴
> - KVM Validation: debug: Unstable: 1 failed test(s): selftest_mptcp_join 🔴
It looks the CI spot a regression with this series (and the previous
version as well):
75 - mptcp_join: remove single address with port
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/12783407981
Do you mind checking that please?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2025-01-15 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 7:01 [PATCH mptcp-next v2 0/7] BPF path manager, part 3 Geliang Tang
2025-01-15 7:01 ` [PATCH mptcp-next v2 1/7] mptcp: add mptcp_pm_genl_fill_addr helper Geliang Tang
2025-01-15 7:01 ` [PATCH mptcp-next v2 2/7] mptcp: add struct mptcp_pm_addr_id_bitmap Geliang Tang
2025-01-15 7:01 ` [PATCH mptcp-next v2 3/7] mptcp: drop inet6_sk in mptcp_nl_find_ssk Geliang Tang
2025-01-15 7:01 ` [PATCH mptcp-next v2 4/7] mptcp: drop match in userspace_pm_append_new_local_addr Geliang Tang
2025-01-15 7:01 ` [PATCH mptcp-next v2 5/7] mptcp: hold msk lock before removing id 0 address Geliang Tang
2025-01-15 7:01 ` [PATCH mptcp-next v2 6/7] mptcp: update address type of get_local_id Geliang Tang
2025-01-15 7:01 ` [PATCH mptcp-next v2 7/7] mptcp: change is_backup interfaces as get_flags Geliang Tang
2025-01-15 8:13 ` [PATCH mptcp-next v2 0/7] BPF path manager, part 3 MPTCP CI
2025-01-15 9:25 ` Matthieu Baerts [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=c8b97326-8cd8-402a-932a-8a0b013eeafa@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@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