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: set endpoint out of transfer: Tests Results
Date: Wed, 31 May 2023 02:24:02 +0000	[thread overview]
Message-ID: <09750f80-8aea-6684-7819-1818d5c57b05@gmail.com> (raw)
In-Reply-To: <6674159f2dbc03ebaf8d64bbf3bd2be270572939.1685494054.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/4720984943493120
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/4720984943493120/summary/summary.txt

- KVM Validation: debug (except selftest_mptcp_join):
  - Unstable: 5 failed test(s): packetdrill_dss packetdrill_fastopen packetdrill_mp_join packetdrill_syscalls selftest_diag 🔴:
  - Task: https://cirrus-ci.com/task/5283934896914432
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5283934896914432/summary/summary.txt

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

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

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


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-31  2:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31  0:52 [PATCH mptcp-next v14 0/7] update userspace pm mptcp_info fields part 2 Geliang Tang
2023-05-31  0:52 ` [PATCH mptcp-next v14 1/7] selftests: mptcp: skip tests when features are not supported Geliang Tang
2023-05-31  0:52 ` [PATCH mptcp-next v14 2/7] mptcp: pass addr to mptcp_pm_alloc_anno_list Geliang Tang
2023-05-31  0:53 ` [PATCH mptcp-next v14 3/7] selftests: mptcp: test userspace pm out of transfer Geliang Tang
2023-05-31  0:53 ` [PATCH mptcp-next v14 4/7] selftests: mptcp: check subflows infos Geliang Tang
2023-05-31  0:53 ` [PATCH mptcp-next v14 5/7] selftests: mptcp: check add_addr infos Geliang Tang
2023-05-31  0:53 ` [PATCH mptcp-next v14 6/7] selftests: mptcp: pass fastclose to sflags Geliang Tang
2023-05-31  0:53 ` [PATCH mptcp-next v14 7/7] selftests: mptcp: set endpoint out of transfer Geliang Tang
2023-05-31  2:24   ` MPTCP CI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-31  8:58 [PATCH mptcp-next v15 " Geliang Tang
2023-05-31 10:28 ` selftests: mptcp: set endpoint out of transfer: Tests Results MPTCP CI
2023-06-07 11:44 [PATCH mptcp-next v17 7/7] selftests: mptcp: set endpoint out of transfer Geliang Tang
2023-06-07 12:48 ` selftests: mptcp: set endpoint out of transfer: Tests Results MPTCP CI
2023-06-16  7:31 [PATCH mptcp-next v20 10/10] selftests: mptcp: set endpoint out of transfer Geliang Tang
2023-06-16  8:37 ` selftests: mptcp: set endpoint out of transfer: Tests Results MPTCP CI
2023-06-19 15:57 ` 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=09750f80-8aea-6684-7819-1818d5c57b05@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