MPTCP Linux Development
 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 "mptcp: register default scheduler": Build Failure
Date: Sat, 08 Oct 2022 04:10:37 +0000	[thread overview]
Message-ID: <448667b9-bc07-5272-b0dc-367cf33cca7d@gmail.com> (raw)
In-Reply-To: <20221008040015.21176-1-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/20221008040015.21176-1-geliang.tang@suse.com/
  https://github.com/multipath-tcp/mptcp_net-next/actions/runs/3209060322

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

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-10-08  4:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08  4:00 [PATCH mptcp-next] Squash to "mptcp: register default scheduler" Geliang Tang
2022-10-08  4:09 ` Squash to "mptcp: register default scheduler": Tests Results MPTCP CI
2022-10-08  4:10 ` MPTCP CI [this message]
2022-10-08  5:17 ` [PATCH mptcp-next] Squash to "mptcp: register default scheduler" kernel test robot
2022-10-08  6:24 ` kernel test robot

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=448667b9-bc07-5272-b0dc-367cf33cca7d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox