All of lore.kernel.org
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: userspace pm: avoid relaunching pm events: Tests Results
Date: Thu, 22 Feb 2024 17:18:05 +0000	[thread overview]
Message-ID: <c67c1936-3d2c-dc00-332e-aa2fd4191a62@gmail.com> (raw)
In-Reply-To: <20240222-selftests-mptcp-shellcheck-v1-6-fed8ba9e6ca6@kernel.org>

Hi Matthieu,

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

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


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)

  reply	other threads:[~2024-02-22 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 16:27 [PATCH mptcp-next 0/6] selftests: mptcp: fix shellcheck warnings Matthieu Baerts (NGI0)
2024-02-22 16:27 ` [PATCH mptcp-next 1/6] selftests: mptcp: diag: " Matthieu Baerts (NGI0)
2024-02-22 16:27 ` [PATCH mptcp-next 2/6] selftests: mptcp: connect: " Matthieu Baerts (NGI0)
2024-02-22 16:27 ` [PATCH mptcp-next 3/6] selftests: mptcp: sockopt: " Matthieu Baerts (NGI0)
2024-02-22 16:28 ` [PATCH mptcp-next 4/6] selftests: mptcp: pm netlink: " Matthieu Baerts (NGI0)
2024-02-22 16:28 ` [PATCH mptcp-next 5/6] selftests: mptcp: simult flows: " Matthieu Baerts (NGI0)
2024-02-22 16:28 ` [PATCH mptcp-next 6/6] selftests: userspace pm: avoid relaunching pm events Matthieu Baerts (NGI0)
2024-02-22 17:18   ` MPTCP CI [this message]
2024-02-22 20:01 ` [PATCH mptcp-next 0/6] selftests: mptcp: fix shellcheck warnings Mat Martineau
2024-02-23 13:35   ` 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=c67c1936-3d2c-dc00-332e-aa2fd4191a62@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=matttbe@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
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.