From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Benjamin Hesmans <benjamin.hesmans@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: test TFO: Build Failure
Date: Thu, 08 Sep 2022 14:10:03 +0000 [thread overview]
Message-ID: <c0d54b09-ae1a-03dd-908e-b7afb82eda33@gmail.com> (raw)
In-Reply-To: <20220908133829.3410092-11-benjamin.hesmans@tessares.net>
Hi Benjamin,
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/20220908133829.3410092-11-benjamin.hesmans@tessares.net/
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/3015610232
Status: failure
Initiator: MPTCPimporter
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/64da39cf5e0a
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)
next prev parent reply other threads:[~2022-09-08 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 13:38 [PATCH RFC mptcp-next 00/10] Implement TCP_FASTOPEN_CONNECT for mptcp Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 01/10] mptcp: add TCP_FASTOPEN_CONNECT socket option Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 02/10] tcp: export tcp_sendmsg_fastopen Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 03/10] mptcp: handle defer connect in mptcp_sendmsg Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 04/10] mptcp: poll allow write call before actual connect Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 05/10] mptcp: delay mptcp data_ack calculation Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 06/10] mptcp: allow delayed " Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 07/10] mptcp: TFO receive: bypass mapping check Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 08/10] mptcp: allow data that can not be DATA_ACKed Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 09/10] mptcp: force data_ready Benjamin Hesmans
2022-09-08 13:38 ` [PATCH RFC mptcp-next 10/10] mptcp: test TFO Benjamin Hesmans
2022-09-08 14:10 ` MPTCP CI [this message]
2022-09-08 15:40 ` mptcp: test TFO: Tests Results 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=c0d54b09-ae1a-03dd-908e-b7afb82eda33@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=benjamin.hesmans@tessares.net \
--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