From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: check IP_TOS in/out are the same: Build Failure
Date: Tue, 23 Nov 2021 11:11:41 +0000 [thread overview]
Message-ID: <fb1fd660-ad41-92c3-bb3b-2e0aad740dc4@gmail.com> (raw)
In-Reply-To: <20211122152651.28466-2-fw@strlen.de>
Hi Florian,
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/20211122152651.28466-2-fw@strlen.de/
https://github.com/multipath-tcp/mptcp_net-next/actions/runs/1494450178
Status: failure
Initiator: matttbe
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/65da757c6e14
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-11-23 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 15:26 [PATCH v2 mptcp-next 1/2] mptcp: getsockopt: add support for IP_TOS Florian Westphal
2021-11-22 15:26 ` [PATCH v2 mptcp-next 2/2] selftests: mptcp: check IP_TOS in/out are the same Florian Westphal
2021-11-22 15:52 ` Matthieu Baerts
2021-11-23 0:01 ` Florian Westphal
2021-11-23 11:11 ` MPTCP CI [this message]
2021-11-23 11:24 ` selftests: mptcp: check IP_TOS in/out are the same: Build Failure Matthieu Baerts
2021-11-23 15:42 ` [PATCH v2 mptcp-next 2/2] selftests: mptcp: check IP_TOS in/out are the same Matthieu Baerts
2021-11-23 7:49 ` [PATCH v2 mptcp-next 1/2] mptcp: getsockopt: add support for IP_TOS Matthieu Baerts
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=fb1fd660-ad41-92c3-bb3b-2e0aad740dc4@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=fw@strlen.de \
--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.