All of lore.kernel.org
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests/bpf: add bpf_rr test: Build Failure
Date: Sat, 28 May 2022 15:21:58 +0000	[thread overview]
Message-ID: <f28fefd1-4e66-d5fc-98c1-3f8094902009@gmail.com> (raw)
In-Reply-To: <1e2b27869e72af5e2928450ff6216f0d78d609da.1653750351.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/1e2b27869e72af5e2928450ff6216f0d78d609da.1653750351.git.geliang.tang@suse.com/
  https://github.com/multipath-tcp/mptcp_net-next/actions/runs/2401426843

Status: failure
Initiator: MPTCPimporter
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/982d66320a49

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)

  reply	other threads:[~2022-05-28 15:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28 15:11 [PATCH mptcp-next v3 00/10] BPF packet scheduler Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 01/10] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 02/10] Squash to "mptcp: add sched in mptcp_sock" Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 03/10] Squash to "mptcp: add get_subflow wrappers" Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 04/10] Squash to "mptcp: add bpf_mptcp_sched_ops" Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 05/10] Squash to "selftests/bpf: add bpf_first scheduler" Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 06/10] Squash to "selftests/bpf: add bpf_first test" Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 07/10] selftests/bpf: add bpf_backup scheduler Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 08/10] selftests/bpf: add bpf_backup test Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 09/10] selftests/bpf: add bpf_rr scheduler Geliang Tang
2022-05-28 15:11 ` [PATCH mptcp-next v3 10/10] selftests/bpf: add bpf_rr test Geliang Tang
2022-05-28 15:21   ` MPTCP CI [this message]
2022-05-28 17:05   ` selftests/bpf: add bpf_rr test: Tests Results MPTCP CI
2022-05-31  9:09 [PATCH mptcp-next v4 10/10] selftests/bpf: add bpf_rr test Geliang Tang
2022-05-31  9:21 ` selftests/bpf: add bpf_rr test: Build Failure MPTCP CI
2022-06-01  6:46 [PATCH mptcp-next v5 11/11] selftests/bpf: add bpf_rr test Geliang Tang
2022-06-01  6:57 ` selftests/bpf: add bpf_rr test: Build Failure MPTCP CI
2022-06-01 14:08 [PATCH mptcp-next v6 11/11] selftests/bpf: add bpf_rr test Geliang Tang
2022-06-01 14:21 ` selftests/bpf: add bpf_rr test: Build Failure MPTCP CI
2022-06-01 15:04   ` Matthieu Baerts
2022-06-01 22:25     ` Geliang Tang
2022-06-02  4:53 [PATCH mptcp-next v7 13/13] selftests/bpf: Add bpf_rr test Geliang Tang
2022-06-02  5:20 ` selftests/bpf: Add bpf_rr test: 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=f28fefd1-4e66-d5fc-98c1-3f8094902009@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.