From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v12 00/10] use bpf_iter in bpf schedulers
Date: Mon, 23 Dec 2024 10:38:59 +0000 [thread overview]
Message-ID: <f660d27e-d20c-5ff2-e59f-dfe6203fb329@gmail.com> (raw)
In-Reply-To: <cover.1734947922.git.tanggeliang@kylinos.cn>
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://github.com/multipath-tcp/mptcp_net-next/actions/runs/12465256771
Status: failure
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/dcde3004d226
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=920379
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)
next prev parent reply other threads:[~2024-12-23 10:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 10:05 [PATCH mptcp-next v12 00/10] use bpf_iter in bpf schedulers Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 01/10] bpf: Add bpf_mptcp_send_info_to_ssk Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 02/10] Revert "mptcp: add sched_data helpers" Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 03/10] mptcp: drop struct mptcp_sched_data Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 04/10] Squash to "bpf: Add bpf_mptcp_sched_ops" Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 05/10] Squash to "bpf: Export mptcp packet scheduler helpers" Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 06/10] Squash to "selftests/bpf: Add bpf_first scheduler & test" Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 07/10] Squash to "selftests/bpf: Add bpf_bkup " Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 08/10] Squash to "selftests/bpf: Add bpf_rr " Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 09/10] Squash to "selftests/bpf: Add bpf_red " Geliang Tang
2024-12-23 10:05 ` [PATCH mptcp-next v12 10/10] Squash to "selftests/bpf: Add bpf_burst " Geliang Tang
2024-12-23 10:38 ` MPTCP CI [this message]
2024-12-23 11:17 ` [PATCH mptcp-next v12 00/10] use bpf_iter in bpf schedulers 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=f660d27e-d20c-5ff2-e59f-dfe6203fb329@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--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