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_first test: Build Failure
Date: Wed, 20 Apr 2022 05:14:41 +0000	[thread overview]
Message-ID: <ee9453e7-0a07-dab8-83f9-827c4552dc73@gmail.com> (raw)
In-Reply-To: <7072b5ca4b8e6d710506a789c4e962c9e33cc54d.1650430389.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/7072b5ca4b8e6d710506a789c4e962c9e33cc54d.1650430389.git.geliang.tang@suse.com/
  https://github.com/multipath-tcp/mptcp_net-next/actions/runs/2193665679

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

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-04-20  5:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  4:56 [PATCH mptcp-next v12 00/10] BPF packet scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 01/10] mptcp: add struct mptcp_sched_ops Geliang Tang
2022-04-20 16:22   ` Matthieu Baerts
2022-04-20  4:57 ` [PATCH mptcp-next v12 02/10] mptcp: register default scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 03/10] mptcp: add a new sysctl scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 04/10] mptcp: add sched in mptcp_sock Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 05/10] mptcp: add get_subflow wrapper Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 06/10] mptcp: add bpf_mptcp_sched_ops Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 07/10] mptcp: add last_snd write access Geliang Tang
2022-04-20 16:23   ` Matthieu Baerts
2022-04-20 16:44   ` Matthieu Baerts
2022-04-21  6:42   ` kernel test robot
2022-04-20  4:57 ` [PATCH mptcp-next v12 08/10] mptcp: add call_me_again flag Geliang Tang
2022-04-20 16:40   ` Matthieu Baerts
2022-04-20  4:57 ` [PATCH mptcp-next v12 09/10] selftests: bpf: add bpf_first scheduler Geliang Tang
2022-04-20  4:57 ` [PATCH mptcp-next v12 10/10] selftests: bpf: add bpf_first test Geliang Tang
2022-04-20  5:14   ` MPTCP CI [this message]
2022-04-20  6:49   ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
  -- strict thread matches above, loose matches on Subject: below --
2022-05-01 13:48 [PATCH mptcp-next v18 7/7] selftests: bpf: add bpf_first test Geliang Tang
2022-05-01 14:12 ` selftests: bpf: add bpf_first test: Build Failure MPTCP CI
2022-03-29  7:09 [PATCH mptcp-next v8 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-03-30 16:54 ` selftests: bpf: add bpf_first test: Build Failure MPTCP CI
2022-03-25 16:12 [PATCH mptcp-next v6 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-03-30 16:54 ` selftests: bpf: add bpf_first 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=ee9453e7-0a07-dab8-83f9-827c4552dc73@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.