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: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL: Tests Results
Date: Sun, 25 Feb 2024 13:51:52 +0000	[thread overview]
Message-ID: <d9003fe1-9240-7ff9-817d-87781339a7de@gmail.com> (raw)
In-Reply-To: <53f87e57c38fe571ca2d41bdf7a225357a6d05ad.1708866087.git.tanggeliang@kylinos.cn>

Hi Geliang,

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/8038266849

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


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)

  reply	other threads:[~2024-02-25 13:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 13:03 [PATCH mptcp-next v3 00/13] add helpers and vars in mptcp_lib.sh, part 3 Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 01/13] selftests: mptcp: capitalize ok/fail/skip Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 02/13] selftests: mptcp: sockopt: print every test result Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 03/13] selftests: mptcp: connect: fix misaligned OK/FAIL Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 04/13] selftests: mptcp: print test results with colors Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 05/13] selftests: mptcp: connect: add dedicated port counter Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 06/13] selftests: mptcp: connect: print out ping tests info Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 07/13] selftests: mptcp: add mptcp_lib_print_test_counter Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 08/13] selftests: mptcp: print test results with counters Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 09/13] selftests: mptcp: move test_fail out of check_expected_one Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 10/13] selftests: mptcp: extract mptcp_lib_check_expected Geliang Tang
2024-02-25 13:03 ` [PATCH mptcp-next v3 11/13] selftests: mptcp: export event macros in mptcp_lib Geliang Tang
2024-02-25 13:04 ` [PATCH mptcp-next v3 12/13] selftests: mptcp: add mptcp_lib_verify_listener_events Geliang Tang
2024-02-25 13:04 ` [PATCH mptcp-next v3 13/13] selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL Geliang Tang
2024-02-25 13:51   ` MPTCP CI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26  9:43 [PATCH mptcp-next v5 12/12] " Geliang Tang
2024-02-26 10:33 ` selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL: Tests Results MPTCP CI
2024-02-26  8:17 [PATCH mptcp-next v4 13/13] selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL Geliang Tang
2024-02-26  9:14 ` selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL: Tests Results MPTCP CI
2024-02-25  9:12 [PATCH mptcp-next v2 13/13] selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL Geliang Tang
2024-02-25 10:05 ` selftests: mptcp: use KSFT_SKIP/KSFT_PASS/KSFT_FAIL: 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=d9003fe1-9240-7ff9-817d-87781339a7de@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