From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v5 0/2] patches for new MPTCP subflow subtest
Date: Wed, 15 May 2024 10:09:24 +0200 [thread overview]
Message-ID: <cba9e588-7ddd-4b69-8636-9666add39aaf@kernel.org> (raw)
In-Reply-To: <8b54db0b-53a4-71b8-2af4-6165802e82f9@gmail.com>
Hi Geliang,
On 15/05/2024 09:08, 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: Success! ✅
> - KVM Validation: debug: Success! ✅
> - KVM Validation: btf (only bpftest_all): Unstable: 2 failed test(s): bpftest_test_progs-cpuv4_mptcp bpftest_test_progs-no_alu32_mptcp 🔴
It looks like the CI doesn't like pm_nl_ctl (good we test that :) ):
> endpoint_init:FAIL:ip netns exec mptcp_ns ./mptcp_pm_nl_ctl add 10.0.1.2 flags subflow unexpected error: 256 (errno 22)
I'm not sure to understand what's wrong. Can you reproduce it on your side?
Note that if you use the Docker image, I recently added the 'bpftests'
command, only to build these tests without the kernel. It should be
useful if you want to check build errors first.
https://github.com/multipath-tcp/mptcp-upstream-virtme-docker/commit/d10b89
(I also added defconfig, selftests, vm-manual, vm-auto, etc. I don't
know if others can be useful.)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-05-15 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 6:18 [PATCH mptcp-next v5 0/2] patches for new MPTCP subflow subtest Geliang Tang
2024-05-15 6:18 ` [PATCH mptcp-next v5 1/2] selftests/bpf: Add mptcp pm_nl_ctl link Geliang Tang
2024-05-15 6:18 ` [PATCH mptcp-next v5 2/2] Squash to "selftests/bpf: Add mptcp subflow subtest" Geliang Tang
2024-05-15 7:08 ` [PATCH mptcp-next v5 0/2] patches for new MPTCP subflow subtest MPTCP CI
2024-05-15 8:09 ` 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=cba9e588-7ddd-4b69-8636-9666add39aaf@kernel.org \
--to=matttbe@kernel.org \
--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 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).