MPTCP Linux Development
 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: mptcp: diag: fix bash warnings on older kernels: Tests Results
Date: Tue, 13 Feb 2024 14:27:32 +0000	[thread overview]
Message-ID: <771cf377-d62c-2a01-03d7-153beeb1e5ea@gmail.com> (raw)
In-Reply-To: <20240207-selftests-mptcp-fix-5-15-v1-3-005b0cdb135a@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/7887523975

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


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-02-13 14:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 18:17 [PATCH mptcp-next 0/3] selftests: mptcp: fixes for issues seen on v5.15.x Matthieu Baerts (NGI0)
2024-02-07 18:17 ` [PATCH mptcp-next 1/3] selftests: mptcp: pm nl: also list skipped tests Matthieu Baerts (NGI0)
2024-02-13 13:35   ` Geliang Tang
2024-02-13 14:59     ` Matthieu Baerts
2024-02-13 15:08       ` Matthieu Baerts
2024-02-07 18:17 ` [PATCH mptcp-next 2/3] selftests: mptcp: pm nl: avoid error msg on older kernels Matthieu Baerts (NGI0)
2024-02-07 18:17 ` [PATCH mptcp-next 3/3] selftests: mptcp: diag: fix bash warnings " Matthieu Baerts (NGI0)
2024-02-07 19:07   ` selftests: mptcp: diag: fix bash warnings on older kernels: Tests Results MPTCP CI
2024-02-07 19:26   ` MPTCP CI
2024-02-13 14:27   ` MPTCP CI [this message]
2024-02-13 15:49   ` 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=771cf377-d62c-2a01-03d7-153beeb1e5ea@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox