From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: listener test for in-kernel PM: Tests Results
Date: Fri, 18 Nov 2022 03:52:40 +0000 [thread overview]
Message-ID: <3a26c64e-1eec-01dc-210b-d8945f0ce299@gmail.com> (raw)
In-Reply-To: <60b6d97a1087057ed07ec1c0c7068e22cede2ad9.1668662624.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:
- Unstable: 1 failed test(s): selftest_simult_flows 🔴:
- Task: https://cirrus-ci.com/task/6178938796376064
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6178938796376064/summary/summary.txt
- KVM Validation: debug:
- Success! ✅:
- Task: https://cirrus-ci.com/task/5924801957593088
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5924801957593088/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/9b92ff8007de
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)
next prev parent reply other threads:[~2022-11-18 3:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 5:31 [PATCH mptcp-next v5 0/4] add pm listener events Geliang Tang
2022-11-17 5:31 ` [PATCH mptcp-next v5 1/4] mptcp: " Geliang Tang
2022-11-17 5:31 ` [PATCH mptcp-next v5 2/4] selftests: mptcp: enhance userspace pm tests Geliang Tang
2022-11-17 5:31 ` [PATCH mptcp-next v5 3/4] selftests: mptcp: listener test for userspace PM Geliang Tang
2022-11-18 1:45 ` Mat Martineau
2022-11-23 11:55 ` Paolo Abeni
2022-11-17 5:31 ` [PATCH mptcp-next v5 4/4] selftests: mptcp: listener test for in-kernel PM Geliang Tang
2022-11-17 8:02 ` selftests: mptcp: listener test for in-kernel PM: Tests Results MPTCP CI
2022-11-18 3:52 ` MPTCP CI [this message]
2022-11-23 11:49 ` [PATCH mptcp-next v5 4/4] selftests: mptcp: listener test for in-kernel PM Paolo Abeni
2022-11-25 2:15 ` Geliang Tang
2022-11-18 1:44 ` [PATCH mptcp-next v5 0/4] add pm listener events Mat Martineau
2022-11-18 2:51 ` Geliang Tang
2022-11-18 10:25 ` Matthieu Baerts
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=3a26c64e-1eec-01dc-210b-d8945f0ce299@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