All of lore.kernel.org
 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: print test results with colors: Tests Results
Date: Fri, 01 Mar 2024 07:40:17 +0000	[thread overview]
Message-ID: <c57e44e0-dced-1b78-cbff-06740df2f5dd@gmail.com> (raw)
In-Reply-To: <6e785c5e53b8749a8bf0cc2402d6575a8b24c42d.1709275290.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/8107769376

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


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-03-01  7:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01  6:46 [PATCH mptcp-next v9 0/6] add helpers and vars in mptcp_lib.sh, part 3 Geliang Tang
2024-03-01  6:46 ` [PATCH mptcp-next v9 1/6] selftests: mptcp: connect: add dedicated port counter Geliang Tang
2024-03-01  6:46 ` [PATCH mptcp-next v9 2/6] selftests: mptcp: connect: fix misaligned output Geliang Tang
2024-03-01  6:46 ` [PATCH mptcp-next v9 3/6] selftests: mptcp: print all error messages to stdout Geliang Tang
2024-03-01  6:46 ` [PATCH mptcp-next v9 4/6] selftests: mptcp: add test counter helpers Geliang Tang
2024-03-01  6:46 ` [PATCH mptcp-next v9 5/6] selftests: mptcp: print test results with counters Geliang Tang
2024-03-01  6:46 ` [PATCH mptcp-next v9 6/6] selftests: mptcp: print test results with colors Geliang Tang
2024-03-01  7:40   ` MPTCP CI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-06  1:40 [PATCH mptcp-next v13 9/9] " Geliang Tang
2024-03-06  2:33 ` selftests: mptcp: print test results with colors: Tests Results MPTCP CI
2024-03-06  2:49 ` MPTCP CI
2024-03-05  5:22 [PATCH mptcp-next v12 9/9] selftests: mptcp: print test results with colors Geliang Tang
2024-03-05  6:12 ` selftests: mptcp: print test results with colors: Tests Results MPTCP CI
2024-03-05  7:07 ` MPTCP CI
2024-03-05 12:13 ` MPTCP CI
2024-03-05 12:31 ` MPTCP CI
2024-03-03 11:52 [PATCH mptcp-next v11 8/8] selftests: mptcp: print test results with colors Geliang Tang
2024-03-03 12:40 ` selftests: mptcp: print test results with colors: Tests Results MPTCP CI
2024-03-03 13:00 ` MPTCP CI
2024-03-03  9:52 [PATCH mptcp-next v10 8/8] selftests: mptcp: print test results with colors Geliang Tang
2024-03-03 10:49 ` selftests: mptcp: print test results with colors: Tests Results MPTCP CI
2024-03-03 11:07 ` MPTCP CI
2024-03-01  6:18 [PATCH mptcp-next v8 6/6] selftests: mptcp: print test results with colors Geliang Tang
2024-03-01  7:25 ` selftests: mptcp: print test results with colors: Tests Results MPTCP CI
2024-02-29  9:51 [PATCH mptcp-next v7 8/8] selftests: mptcp: print test results with colors Geliang Tang
2024-02-29 10:43 ` selftests: mptcp: print test results with colors: 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=c57e44e0-dced-1b78-cbff-06740df2f5dd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.