MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Edward Liaw <edliaw@google.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH v2 0/5] Define _GNU_SOURCE for sources using
Date: Tue, 07 May 2024 22:35:19 +0000	[thread overview]
Message-ID: <c9810477-27da-5322-7bb1-c1a4af6ceb05@gmail.com> (raw)
In-Reply-To: <20240507214254.2787305-1-edliaw@google.com>

Hi Edward,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: normal: Success! ✅
- KVM Validation: debug: Success! ✅
- KVM Validation: btf (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/8992857887

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/13e61f25eef2
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=851355


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)

  parent reply	other threads:[~2024-05-07 22:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 21:38 [PATCH v2 0/5] Define _GNU_SOURCE for sources using Edward Liaw
2024-05-07 21:38 ` [PATCH v2 1/5] selftests: Compile kselftest headers with -D_GNU_SOURCE Edward Liaw
2024-05-08  7:48   ` Muhammad Usama Anjum
2024-05-08 12:05   ` Mark Brown
2024-05-08 21:23   ` John Hubbard
2024-05-07 21:38 ` [PATCH v2 2/5] selftests/sgx: Include KHDR_INCLUDES in Makefile Edward Liaw
2024-05-08  7:49   ` Muhammad Usama Anjum
2024-05-08 15:33   ` Dave Hansen
2024-05-08 16:44     ` Jarkko Sakkinen
2024-05-08 21:25   ` John Hubbard
2024-05-07 21:38 ` [PATCH v2 3/5] selftests: " Edward Liaw
2024-05-07 22:36   ` Jarkko Sakkinen
2024-05-08  7:49   ` Muhammad Usama Anjum
2024-05-08 21:41   ` John Hubbard
2024-05-09  0:29     ` Edward Liaw
2024-05-09  1:03       ` John Hubbard
2024-05-09  5:14   ` Mark Brown
2024-05-07 21:38 ` [PATCH v2 4/5] selftests: Drop define _GNU_SOURCE Edward Liaw
2024-05-08  7:50   ` Muhammad Usama Anjum
2024-05-08 13:54   ` Sean Christopherson
2024-05-08 20:27     ` Edward Liaw
2024-05-08 21:39   ` John Hubbard
2024-05-07 21:38 ` [PATCH v2 5/5] selftests: Drop duplicate -D_GNU_SOURCE Edward Liaw
2024-05-08  7:58   ` Muhammad Usama Anjum
2024-05-08 21:49   ` John Hubbard
2024-05-07 22:35 ` MPTCP CI [this message]
2024-05-07 23:28 ` [PATCH v2 0/5] Define _GNU_SOURCE for sources using Kees Cook
2024-05-08 13:47 ` Sean Christopherson
2024-05-08 18:03   ` Edward Liaw
2024-05-08 23:10 ` Shuah Khan
2024-05-09  6:13   ` Edward Liaw
2024-05-09 14:37     ` Shuah Khan
2024-05-09 17:45       ` Edward Liaw
2024-05-09 18:20         ` Muhammad Usama Anjum

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=c9810477-27da-5322-7bb1-c1a4af6ceb05@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=edliaw@google.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