From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: update pm_nl_ctl usage header: Tests Results
Date: Thu, 16 Jun 2022 06:32:41 +0000 [thread overview]
Message-ID: <453d4949-497c-21a6-dd52-012ad98b712d@gmail.com> (raw)
In-Reply-To: <11468cbfc4fc4ca766094b81c544f9108e04daf2.1655355422.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:
- Success! ✅:
- Task: https://cirrus-ci.com/task/6339386420756480
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6339386420756480/summary/summary.txt
- KVM Validation: debug:
- Unstable: 2 failed test(s): packetdrill_sockopts selftest_diag 🔴:
- Task: https://cirrus-ci.com/task/4932011537203200
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4932011537203200/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/d4a1e2c951f3
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-06-16 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 5:02 [PATCH mptcp-next v3 0/5] mptcp_join userspace pm tests Geliang Tang
2022-06-16 5:02 ` [PATCH mptcp-next v3 1/5] mptcp: update MIB_RMSUBFLOW in cmd_sf_destroy Geliang Tang
2022-06-16 5:02 ` [PATCH mptcp-next v3 2/5] selftests: mptcp: userspace pm address tests Geliang Tang
2022-06-16 5:02 ` [PATCH mptcp-next v3 3/5] selftests: mptcp: userspace pm subflow tests Geliang Tang
2022-06-17 22:10 ` Mat Martineau
2022-06-20 16:52 ` Matthieu Baerts
2022-06-20 18:27 ` Mat Martineau
2022-06-16 5:02 ` [PATCH mptcp-next v3 4/5] selftests: mptcp: avoid Terminated messages in userspace_pm Geliang Tang
2022-06-16 5:02 ` [PATCH mptcp-next v3 5/5] selftests: mptcp: update pm_nl_ctl usage header Geliang Tang
2022-06-16 6:32 ` MPTCP CI [this message]
2022-06-17 22:11 ` [PATCH mptcp-next v3 0/5] mptcp_join userspace pm tests Mat Martineau
2022-06-20 16:53 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2022-06-11 14:54 [PATCH mptcp-next v2 5/5] selftests: mptcp: update pm_nl_ctl usage header Geliang Tang
2022-06-11 16:55 ` selftests: mptcp: update pm_nl_ctl usage header: Tests Results MPTCP CI
2022-06-10 5:45 [PATCH mptcp-next] selftests: mptcp: update pm_nl_ctl usage header Geliang Tang
2022-06-10 7:11 ` selftests: mptcp: update pm_nl_ctl usage header: 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=453d4949-497c-21a6-dd52-012ad98b712d@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