MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: rm subflow with v4/v4mapped addr: Tests Results
Date: Tue, 06 Feb 2024 07:30:31 +0000	[thread overview]
Message-ID: <1df897c7-3617-89ad-d9f7-00ec964414e1@gmail.com> (raw)
In-Reply-To: <683704e855c0b54d003d6d635d0850aab0b71525.1707198093.git.tanggeliang@kylinos.cn>

Hi Geliang,

Thank you for your modifications, that's great!

Our CI (Cirrus) did some validations with a debug kernel and here is its report:

- KVM Validation: debug (except selftest_mptcp_join):
  - Success! ✅:
  - Task: https://cirrus-ci.com/task/6515054728708096
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/6515054728708096/summary/summary.txt

- KVM Validation: debug (only selftest_mptcp_join):
  - Success! ✅:
  - Task: https://cirrus-ci.com/task/5054167002120192
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5054167002120192/summary/summary.txt

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


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-debug

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-06  7:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06  5:43 [PATCH mptcp-next v2 0/2] fixes for "map v4 address to v6" Geliang Tang
2024-02-06  5:43 ` [PATCH mptcp-next v2 1/2] mptcp: map v4 address to v6 when destroying subflow Geliang Tang
2024-02-06  5:43 ` [PATCH mptcp-next v2 2/2] selftests: mptcp: rm subflow with v4/v4mapped addr Geliang Tang
2024-02-06  6:43   ` selftests: mptcp: rm subflow with v4/v4mapped addr: Tests Results MPTCP CI
2024-02-06  7:30   ` MPTCP CI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-07  1:55 [PATCH mptcp-next v3 2/2] selftests: mptcp: rm subflow with v4/v4mapped addr Geliang Tang
2024-02-07  2:49 ` selftests: mptcp: rm subflow with v4/v4mapped addr: Tests Results MPTCP CI
2024-02-07  3:11 ` MPTCP CI
2024-02-14  2:36 ` MPTCP CI
2024-02-14  2:55 ` MPTCP CI
2024-02-01  3:51 [PATCH mptcp-net 4/4] selftests: mptcp: rm subflow with v4/v4mapped addr Geliang Tang
2024-02-01  4:40 ` selftests: mptcp: rm subflow with v4/v4mapped addr: Tests Results MPTCP CI
2024-02-01  5:01 ` MPTCP CI
2024-02-06  2:21 ` MPTCP CI
2024-02-06  2:38 ` MPTCP CI
2023-11-28 14:22 [PATCH mptcp-next v13 32/32] selftests: mptcp: rm subflow with v4/v4mapped addr Geliang Tang
2023-11-28 14:33 ` selftests: mptcp: rm subflow with v4/v4mapped addr: Tests Results MPTCP CI
2023-12-04 20:35 ` 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=1df897c7-3617-89ad-d9f7-00ec964414e1@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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