All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed

From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: MAINTAINERS: update Geliang's email address: Tests Results
Date: Thu, 01 Feb 2024 02:00:44 +0000	[thread overview]
Message-ID: <f60700a1-5fb1-c6f6-9d89-f59b159e4ec3@gmail.com> (raw)
In-Reply-To: <eb152068d96e0980d010272f5190da7807f35c13.1706749536.git.geliang@kernel.org>

Hi Geliang,

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/7734828846

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/2a536c07d503


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-01  2:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  1:06 [PATCH mptcp-net] MAINTAINERS: update Geliang's email address Geliang Tang
2024-02-01  2:00 ` MPTCP CI [this message]
2024-02-01  3:14 ` MAINTAINERS: update Geliang's email address: Tests Results MPTCP CI
2024-02-02  9:19 ` [PATCH mptcp-net] MAINTAINERS: update Geliang's email address Matthieu Baerts
2024-02-02 11:39   ` 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=f60700a1-5fb1-c6f6-9d89-f59b159e4ec3@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=geliang@kernel.org \
    --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

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.