mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Dmytro SHYTYI <dmytro@shytyi.net>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: Fast Open Mechanism: Build Failure
Date: Mon, 01 Aug 2022 02:57:53 +0000	[thread overview]
Message-ID: <d63beeaa-afd5-5a12-3b6c-504956cab06b@gmail.com> (raw)
In-Reply-To: <20220801024656.397714-1-dmytro@shytyi.net>

Hi Dmytro,

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/20220801024656.397714-1-dmytro@shytyi.net/
  https://github.com/multipath-tcp/mptcp_net-next/actions/runs/2771932806

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

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-08-01  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  2:46 [RFC PATCH mptcp-next v4] mptcp: Fast Open Mechanism Dmytro SHYTYI
2022-08-01  2:57 ` MPTCP CI [this message]
2022-08-01  2:59 ` mptcp: Fast Open Mechanism: Tests Results MPTCP CI
2022-08-03  0:32 ` [RFC PATCH mptcp-next v4] mptcp: Fast Open Mechanism Mat Martineau
2022-08-03  7:36   ` Dmytro SHYTYI
  -- strict thread matches above, loose matches on Subject: below --
2022-05-22 18:39 [RFC PATCH mptcp-next v3] " Dmytro SHYTYI
2022-05-22 18:47 ` mptcp: Fast Open Mechanism: 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=d63beeaa-afd5-5a12-3b6c-504956cab06b@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=dmytro@shytyi.net \
    --cc=mptcp@lists.linux.dev \
    --subject='Re: mptcp: Fast Open Mechanism: Build Failure' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).