MPTCP Linux Development
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: do endpoint manipulation out of transfer: Tests Results
Date: Thu, 04 May 2023 11:33:24 +0000	[thread overview]
Message-ID: <cc424207-19c8-181d-7a76-73dde896b699@gmail.com> (raw)
In-Reply-To: <2be8d0226ca5ac72b1801eb128fa9028d4886b46.1683195386.git.geliang.tang@suse.com>

Hi Geliang,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

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

- KVM Validation: debug (only selftest_mptcp_join):
  - Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
  - Task: https://cirrus-ci.com/task/6716480637632512
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/6716480637632512/summary/summary.txt

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

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

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


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 (Tessares)

  reply	other threads:[~2023-05-04 11:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 10:20 [PATCH mptcp-next v11 00/12] update userspace pm mptcp_info fields Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 01/12] mptcp: only send RM_ADDR in nl_cmd_remove Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 02/12] selftests: mptcp: update userspace pm addr tests Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 03/12] mptcp: export remove_anno_list_by_saddr Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 04/12] mptcp: add addr into userspace pm list Geliang Tang
2023-05-04 10:57   ` Geliang Tang
2023-05-04 14:59   ` Matthieu Baerts
2023-05-17 15:26     ` Matthieu Baerts
2023-05-04 10:20 ` [PATCH mptcp-next v11 05/12] selftests: mptcp: update userspace pm subflow tests Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 06/12] mptcp: update userspace pm infos Geliang Tang
2023-05-04 10:59   ` Geliang Tang
2023-05-04 12:46     ` Matthieu Baerts
2023-05-04 15:02   ` Matthieu Baerts
2023-05-04 10:20 ` [PATCH mptcp-next v11 07/12] selftests: mptcp: do userspace tests out of transfer Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 08/12] selftests: mptcp: check subflows infos Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 09/12] selftests: mptcp: check add_addr infos Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 10/12] mptcp: pass addr to mptcp_pm_alloc_anno_list Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 11/12] selftests: mptcp: pass fastclose to sflags Geliang Tang
2023-05-04 10:20 ` [PATCH mptcp-next v11 12/12] selftests: mptcp: do endpoint manipulation out of transfer Geliang Tang
2023-05-04 11:33   ` MPTCP CI [this message]
2023-05-04 14:57 ` [PATCH mptcp-next v11 00/12] update userspace pm mptcp_info fields Matthieu Baerts
  -- strict thread matches above, loose matches on Subject: below --
2023-05-06  5:09 [PATCH mptcp-next v12 12/12] selftests: mptcp: do endpoint manipulation out of transfer Geliang Tang
2023-05-06  6:04 ` selftests: mptcp: do endpoint manipulation out of transfer: Tests Results 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=cc424207-19c8-181d-7a76-73dde896b699@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=geliang.tang@suse.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