From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: mptcp@lists.linux.dev
Subject: Re: net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit.: Tests Results
Date: Thu, 15 Feb 2024 10:58:07 +0000 [thread overview]
Message-ID: <970ce17f-2ba1-4e55-d483-086eede37a59@gmail.com> (raw)
In-Reply-To: <20240214195407.3175-1-kuniyu@amazon.com>
Hi Kuniyuki,
Thank you for your modifications, that's great!
Our CI (GitHub Action) did some validations and here is its report:
- KVM Validation: normal:
- Success! ✅:
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/7914279679
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/4b23a08aba91
If there are some issues, you can reproduce them using the same environment as
the one used by the CI thanks to a docker image, e.g.:
$ cd [kernel source code]
$ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
--pull always mptcp/mptcp-upstream-virtme-docker:latest \
auto-normal
For more details:
https://github.com/multipath-tcp/mptcp-upstream-virtme-docker
Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)
Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)
next prev parent reply other threads:[~2024-02-15 10:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 19:54 [PATCH v2 net-next] net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit Kuniyuki Iwashima
2024-02-14 20:50 ` net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit.: Tests Results MPTCP CI
2024-02-14 21:04 ` MPTCP CI
2024-02-15 9:58 ` [PATCH v2 net-next] net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit Matthieu Baerts
2024-02-15 19:37 ` Kuniyuki Iwashima
2024-02-15 10:58 ` MPTCP CI [this message]
2024-02-15 11:13 ` net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit.: Tests Results MPTCP CI
2024-02-15 14:14 ` [PATCH v2 net-next] net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit Alexandra Winter
2024-02-15 19:39 ` Kuniyuki Iwashima
2024-02-15 15:07 ` Jakub Kicinski
2024-02-15 16:05 ` Paolo Abeni
2024-02-15 16:10 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 22:31 [PATCH v1 " Kuniyuki Iwashima
2024-02-13 23:30 ` net: Deprecate SO_DEBUG and reclaim SOCK_DBG bit.: Tests Results MPTCP CI
2024-02-14 1:03 ` MPTCP CI
2024-02-14 9:14 ` MPTCP CI
2024-02-14 9:29 ` 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=970ce17f-2ba1-4e55-d483-086eede37a59@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=kuniyu@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox