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: Squash to "selftests/bpf: Add bpf_rr scheduler": Build Failure
Date: Wed, 16 Nov 2022 01:01:10 +0000	[thread overview]
Message-ID: <d8266a35-2174-e41d-3448-9871c57963bb@gmail.com> (raw)
In-Reply-To: <d1d8d0acb444c6ac39eb6ae945bf439d633e74b3.1668151131.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/d1d8d0acb444c6ac39eb6ae945bf439d633e74b3.1668151131.git.geliang.tang@suse.com/
  https://github.com/multipath-tcp/mptcp_net-next/actions/runs/3475381466

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

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)

  parent reply	other threads:[~2022-11-16  1:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  7:47 [PATCH mptcp-next v19 0/9] BPF redundant scheduler, part 1 Geliang Tang
2022-11-11  7:47 ` [PATCH mptcp-next v19 1/9] mptcp: refactor push_pending logic Geliang Tang
2022-11-11  7:47 ` [PATCH mptcp-next v19 2/9] mptcp: drop last_snd and MPTCP_RESET_SCHEDULER Geliang Tang
2022-11-11  7:47 ` [PATCH mptcp-next v19 3/9] mptcp: add sched_data_set_contexts helper Geliang Tang
2022-11-18 18:10   ` Matthieu Baerts
2022-11-18 18:26     ` Mat Martineau
2022-11-18 22:15       ` Geliang Tang
2022-11-11  7:47 ` [PATCH mptcp-next v19 4/9] Squash to "mptcp: add struct mptcp_sched_ops" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 5/9] Squash to "bpf: Add bpf_mptcp_sched_ops" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 6/9] Squash to "bpf: Add bpf_mptcp_sched_kfunc_set" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 7/9] Squash to "selftests/bpf: Add bpf_first scheduler" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 8/9] Squash to "selftests/bpf: Add bpf_bkup scheduler" Geliang Tang
2022-11-11  7:48 ` [PATCH mptcp-next v19 9/9] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-11-11  8:12   ` Squash to "selftests/bpf: Add bpf_rr scheduler": Build Failure MPTCP CI
2022-11-11  9:53   ` Squash to "selftests/bpf: Add bpf_rr scheduler": Tests Results MPTCP CI
2022-11-16  1:01   ` MPTCP CI [this message]
2022-11-16  2:38   ` MPTCP CI
2022-11-16  0:41 ` [PATCH mptcp-next v19 0/9] BPF redundant scheduler, part 1 Mat Martineau
2022-11-16  2:17   ` Geliang Tang
2022-11-18 14:52 ` Matthieu Baerts
2022-11-18 15:12   ` Geliang Tang
2022-12-09  3:18   ` Geliang Tang
2022-12-14 17:34     ` Matthieu Baerts
  -- strict thread matches above, loose matches on Subject: below --
2022-10-14 13:32 [PATCH mptcp-next v8 15/15] Squash to "selftests/bpf: Add bpf_rr scheduler" Geliang Tang
2022-10-14 14:18 ` Squash to "selftests/bpf: Add bpf_rr 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=d8266a35-2174-e41d-3448-9871c57963bb@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.