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: Tue, 05 Mar 2024 12:31:19 +0000 [thread overview]
Message-ID: <14b7d8b1-a141-71a0-3bea-7d5bac88156c@gmail.com> (raw)
In-Reply-To: <9a0667639ecd47b8f8bc9370136e53f4d3caef79.1709615883.git.tanggeliang@kylinos.cn>
Hi Geliang,
Thank you for your modifications, that's great!
Our CI (Cirrus) did some validations with a debug kernel and here is its report:
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6300162599944192
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6300162599944192/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/4892787716390912
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4892787716390912/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/bccac410551e
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 (NGI0 Core)
next prev parent reply other threads:[~2024-03-05 12:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 5:21 [PATCH mptcp-next v12 0/9] add helpers and vars in mptcp_lib.sh, part 3 Geliang Tang
2024-03-05 5:21 ` [PATCH mptcp-next v12 1/9] selftests: mptcp: print all error messages to stdout Geliang Tang
2024-03-05 5:22 ` [PATCH mptcp-next v12 2/9] selftests: mptcp: connect: add dedicated port counter Geliang Tang
2024-03-05 5:22 ` [PATCH mptcp-next v12 3/9] selftests: mptcp: connect: fix misaligned output Geliang Tang
2024-03-05 5:22 ` [PATCH mptcp-next v12 4/9] selftests: mptcp: sockopt: print every test result Geliang Tang
2024-03-05 5:22 ` [PATCH mptcp-next v12 5/9] selftests: mptcp: export TEST_COUNTER variable Geliang Tang
2024-03-05 5:22 ` [PATCH mptcp-next v12 6/9] selftests: mptcp: add print_title in mptcp_lib Geliang Tang
2024-03-05 5:22 ` [PATCH mptcp-next v12 7/9] selftests: mptcp: print test results with counters Geliang Tang
2024-03-05 5:22 ` [PATCH mptcp-next v12 8/9] selftests: mptcp: connect: use += operator to append strings Geliang Tang
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-06 1:40 [PATCH mptcp-next v13 9/9] selftests: mptcp: print test results with colors 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-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:46 [PATCH mptcp-next v9 6/6] selftests: mptcp: print test results with colors Geliang Tang
2024-03-01 7:40 ` selftests: mptcp: print test results with colors: Tests Results 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=14b7d8b1-a141-71a0-3bea-7d5bac88156c@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).