From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@linux.dev>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: flush userspace addrs list: Build Failure
Date: Fri, 29 Dec 2023 13:17:48 +0000 [thread overview]
Message-ID: <69482924-45bb-d457-a75c-a154b49cb7cc@gmail.com> (raw)
In-Reply-To: <33341ee1f12b97eb0369c4ea6c84c4b99f03eb8e.1703853513.git.geliang.tang@linux.dev>
Hi Geliang,
Thank you for your modifications, that's great!
But sadly, our CI spotted some issues with it when trying to build it.
You can find more details there:
https://patchwork.kernel.org/project/mptcp/patch/33341ee1f12b97eb0369c4ea6c84c4b99f03eb8e.1703853513.git.geliang.tang@linux.dev/
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/7356843701
Status: failure
Initiator: MPTCPimporter
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/5fbf3fd9eabf
Feel free to reply to this email if you cannot access logs, if you need
some support to fix the error, if this doesn't seem to be caused by your
modifications or if the error is a false positive one.
Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)
prev parent reply other threads:[~2023-12-29 13:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 12:47 [PATCH mptcp-next v6 00/24] dump for userspace pm Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 01/24] mptcp: set set_id flag when parsing addr Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 02/24] mptcp: parse userspace pm entry to get flags Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 03/24] mptcp: test set_id flag when appending addr Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 04/24] mptcp: check addrs list in userspace_pm_get_local_id Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 05/24] mptcp: map v4 address to v6 when destroying subflow Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 06/24] selftests: mptcp: rm subflow with v4/v4mapped addr Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 07/24] mptcp: export mptcp_genl_family & mptcp_nl_fill_addr Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 08/24] mptcp: implement mptcp_userspace_pm_dump_addr Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 09/24] mptcp: add token for get-addr in yaml Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 10/24] mptcp: dump addrs in userspace pm list Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 11/24] mptcp: check userspace pm subflow flag Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 12/24] selftests: mptcp: add " Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 13/24] selftests: mptcp: add token for dump_addr Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 14/24] selftests: mptcp: add check_output helper Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 15/24] selftests: mptcp: dump after creating id 0 subflow Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 16/24] selftests: mptcp: dump userspace addrs list Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 17/24] mptcp: add userspace_pm_lookup_addr_by_id helper Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 18/24] mptcp: implement mptcp_userspace_pm_get_addr Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 19/24] mptcp: get addr in userspace pm list Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 20/24] selftests: mptcp: add token for get_addr Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 21/24] selftests: mptcp: userspace pm get addr tests Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 22/24] mptcp: update set_flags interfaces Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 23/24] mptcp: set error messages for set_flags Geliang Tang
2023-12-29 12:47 ` [PATCH mptcp-next v6 24/24] selftests: mptcp: flush userspace addrs list Geliang Tang
2023-12-29 13:17 ` 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=69482924-45bb-d457-a75c-a154b49cb7cc@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=geliang.tang@linux.dev \
--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 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.