From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Dmytro Shytyi <dmytro@shytyi.net>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptfo initiator/listener: Build Failure
Date: Thu, 06 Oct 2022 12:51:37 +0000 [thread overview]
Message-ID: <3436b3c1-c5dc-18bc-8e75-786fa8d1b3df@gmail.com> (raw)
In-Reply-To: <20221001031502.29152-8-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/20221001031502.29152-8-dmytro@shytyi.net/
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/3197013753
Status: failure
Initiator: MPTCPimporter
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/7c22bca6e0ab
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-10-06 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 3:14 [RFC PATCH mptcp-next v13 0/7] mptcp: Fast Open Mechanism Dmytro Shytyi
2022-10-01 3:14 ` [RFC PATCH mptcp-next v13 1/7] mptcp: add __mptcp_pre_connect() helper Dmytro Shytyi
2022-10-01 3:14 ` [RFC PATCH mptcp-next v13 2/7] mptcp: add __mptcp_stream_connect() helper Dmytro Shytyi
2022-10-01 3:14 ` [RFC PATCH mptcp-next v13 3/7] mptcp: introduce MSG_FASTOPEN flag Dmytro Shytyi
2022-10-01 3:14 ` [RFC PATCH mptcp-next v13 4/7] mptcp: implement delayed seq generation for passive fastopen Dmytro Shytyi
2022-10-01 3:15 ` [RFC PATCH mptcp-next v13 5/7] mptcp: add subflow_v(4,6)_send_synack() Dmytro Shytyi
2022-10-01 3:15 ` [RFC PATCH mptcp-next v13 6/7] mptcp: add TCP_FASTOPEN sock option Dmytro Shytyi
2022-10-01 3:15 ` [RFC PATCH mptcp-next v13 7/7] selftests: mptfo initiator/listener Dmytro Shytyi
2022-10-06 12:51 ` MPTCP CI [this message]
2022-10-06 15:16 ` selftests: mptfo initiator/listener: Tests Results MPTCP CI
-- strict thread matches above, loose matches on Subject: below --
2022-09-27 22:53 [RFC PATCH mptcp-next v12 7/7] selftests: mptfo initiator/listener Dmytro Shytyi
2022-09-27 23:23 ` selftests: mptfo initiator/listener: Build Failure MPTCP CI
2022-09-21 12:55 [RFC PATCH mptcp-next v9 6/6] selftests: mptfo initiator/listener Dmytro Shytyi
2022-09-21 13:38 ` selftests: mptfo initiator/listener: Build Failure MPTCP CI
2022-09-20 12:52 [RFC PATCH mptcp-next v8 7/7] selftests: mptfo initiator/listener Dmytro Shytyi
2022-09-20 13:17 ` selftests: mptfo initiator/listener: Build Failure MPTCP CI
2022-09-15 23:56 [RFC PATCH mptcp-next v6 9/9] selftests: mptfo initiator/listener Dmytro Shytyi
2022-09-16 1:35 ` selftests: mptfo initiator/listener: 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=3436b3c1-c5dc-18bc-8e75-786fa8d1b3df@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=dmytro@shytyi.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;
as well as URLs for NNTP newsgroup(s).