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: add mptcp_lib_wait_local_port_listen: Tests Results
Date: Fri, 13 Oct 2023 09:28:49 +0000	[thread overview]
Message-ID: <5ee51fbd-c733-933c-3ba1-3bff7ecda252@gmail.com> (raw)
In-Reply-To: <71949d82783458d066f4d49bdc5a0e24d8687e04.1697182955.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/6377983343067136
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/6377983343067136/summary/summary.txt

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

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

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

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


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-10-13  9:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  7:44 [PATCH mptcp-next v4 0/7] export helpers to mptcp_lib.sh Geliang Tang
2023-10-13  7:44 ` [PATCH mptcp-next v4 1/7] selftests: mptcp: add mptcp_lib_kill_wait Geliang Tang
2023-10-13  7:44 ` [PATCH mptcp-next v4 2/7] selftests: mptcp: add mptcp_lib_is_v6 Geliang Tang
2023-10-13  7:44 ` [PATCH mptcp-next v4 3/7] selftests: mptcp: add mptcp_lib_get_counter Geliang Tang
2023-10-13  7:44 ` [PATCH mptcp-next v4 4/7] selftests: mptcp: add missing oflag=append Geliang Tang
2023-10-13  7:44 ` [PATCH mptcp-next v4 5/7] selftests: mptcp: add mptcp_lib_make_file Geliang Tang
2023-10-22 23:25   ` Matthieu Baerts
2023-10-13  7:44 ` [PATCH mptcp-next v4 6/7] selftests: mptcp: add mptcp_lib_check_transfer Geliang Tang
2023-10-13  7:44 ` [PATCH mptcp-next v4 7/7] selftests: mptcp: add mptcp_lib_wait_local_port_listen Geliang Tang
2023-10-13  9:28   ` MPTCP CI [this message]
2023-10-22 23:30 ` [PATCH mptcp-next v4 0/7] export helpers to mptcp_lib.sh Matthieu Baerts
2023-10-22 23:48 ` Matthieu Baerts
  -- strict thread matches above, loose matches on Subject: below --
2023-09-25  8:42 [PATCH mptcp-next v3 29/29] selftests: mptcp: add mptcp_lib_wait_local_port_listen Geliang Tang
2023-09-25  9:54 ` selftests: mptcp: add mptcp_lib_wait_local_port_listen: Tests Results MPTCP CI
2023-09-28 22:04 ` MPTCP CI
2023-09-19  4:02 [PATCH mptcp-next v2 30/30] selftests: mptcp: add mptcp_lib_wait_local_port_listen Geliang Tang
2023-09-19  6:00 ` selftests: mptcp: add mptcp_lib_wait_local_port_listen: 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=5ee51fbd-c733-933c-3ba1-3bff7ecda252@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