From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: Squash to "selftests/bpf: Add bpf_burst scheduler": Build Failure
Date: Tue, 15 Aug 2023 06:41:43 +0000 [thread overview]
Message-ID: <9fc8d79d-dd15-db46-9edc-2ca23b74a626@gmail.com> (raw)
In-Reply-To: <6608f9d9fea9d2bc57ec8378a7afa4fd52c66d17.1692080803.git.geliang.tang@suse.com>
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/6608f9d9fea9d2bc57ec8378a7afa4fd52c66d17.1692080803.git.geliang.tang@suse.com/
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/5864337382
Status: failure
Initiator: MPTCPimporter
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/538d21adcc61
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 (Tessares)
next prev parent reply other threads:[~2023-08-15 6:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 6:29 [PATCH mptcp-next 0/9] Update scheduler refactor commits Geliang Tang
2023-08-15 6:29 ` [PATCH mptcp-next 1/9] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2023-08-15 6:29 ` [PATCH mptcp-next 2/9] Squash to "mptcp: add scheduler wrappers" Geliang Tang
2023-08-15 6:29 ` [PATCH mptcp-next 3/9] Squash to "mptcp: register default scheduler" Geliang Tang
2023-08-15 6:29 ` [PATCH mptcp-next 4/9] Squash to "selftests/bpf: Add mptcp sched structs" Geliang Tang
2023-08-15 6:29 ` [PATCH mptcp-next 5/9] Squash to "selftests/bpf: Add bpf_first scheduler" Geliang Tang
2023-08-15 6:29 ` [PATCH mptcp-next 6/9] Squash to "selftests/bpf: Add bpf_bkup scheduler" Geliang Tang
2023-08-15 6:29 ` [PATCH mptcp-next 7/9] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2023-08-15 6:29 ` [PATCH mptcp-next 8/9] Squash to "selftests/bpf: Add bpf_red scheduler" Geliang Tang
2023-08-15 6:29 ` [PATCH mptcp-next 9/9] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-08-15 6:41 ` MPTCP CI [this message]
2023-08-15 7:44 ` Squash to "selftests/bpf: Add bpf_burst scheduler": Tests Results MPTCP CI
2023-08-17 0:07 ` [PATCH mptcp-next 0/9] Update scheduler refactor commits Mat Martineau
2023-08-17 9:30 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2023-08-03 4:27 [PATCH mptcp-next v3 6/6] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-08-03 4:53 ` Squash to "selftests/bpf: Add bpf_burst scheduler": Build Failure MPTCP CI
2023-08-02 11:55 [PATCH mptcp-next v2 6/6] Squash to "selftests/bpf: Add bpf_burst scheduler" Geliang Tang
2023-08-02 12:22 ` Squash to "selftests/bpf: Add bpf_burst scheduler": Build Failure 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=9fc8d79d-dd15-db46-9edc-2ca23b74a626@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=geliang.tang@suse.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 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.