From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Davide Caratti <dcaratti@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: fix corrupt receiver key in MPC + data + checksum: Build Failure
Date: Tue, 26 Oct 2021 05:08:00 +0000 [thread overview]
Message-ID: <d451b4e9-b44c-e496-4401-ce769a91db0f@gmail.com> (raw)
In-Reply-To: <1207c7d44dd4d1a630afc8b7018cf4185fe4a489.1634827708.git.dcaratti@redhat.com>
Hi Davide,
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://github.com/multipath-tcp/mptcp_net-next/actions/runs/1384159937
Status: failure
Initiator: MPTCPimporter
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/8d20a4498bfc
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
next prev parent reply other threads:[~2021-10-26 5:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 14:51 [PATCH mptcp-net] mptcp: fix corrupt receiver key in MPC + data + checksum Davide Caratti
2021-10-21 15:00 ` mptcp: fix corrupt receiver key in MPC + data + checksum: Build Failure MPTCP CI
2021-10-21 15:37 ` [PATCH mptcp-net] mptcp: fix corrupt receiver key in MPC + data + checksum Matthieu Baerts
2021-10-22 23:22 ` Mat Martineau
2021-10-26 4:56 ` kernel test robot
2021-10-26 4:56 ` kernel test robot
2021-10-26 5:08 ` MPTCP CI [this message]
2021-10-26 9:11 ` mptcp: fix corrupt receiver key in MPC + data + checksum: Build Failure MPTCP CI
[not found] <essaresCI<no-reply@tessares.net>
[not found] ` <essares CI <no-reply@tessares.net>
2021-10-21 15:51 ` 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=d451b4e9-b44c-e496-4401-ce769a91db0f@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=dcaratti@redhat.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.