From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: add test-cases for mixed v4/v6 subflows: Tests Results
Date: Fri, 23 Dec 2022 13:58:34 +0000 [thread overview]
Message-ID: <2cdb8605-6f9d-2298-bbe4-c55afe2cabdb@gmail.com> (raw)
In-Reply-To: <c2b08053101c90d85634c95840e3a8a637fa8346.1671799401.git.pabeni@redhat.com>
Hi Paolo,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- KVM Validation: normal (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/4957635586293760
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4957635586293760/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6083535493136384
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6083535493136384/summary/summary.txt
- KVM Validation: Script error! ❓:
- :
- Task: https://cirrus-ci.com/task/6646485446557696
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6646485446557696/summary/summary.txt
- KVM Validation: Script error! ❓:
- :
- Task: https://cirrus-ci.com/task/5520585539715072
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5520585539715072/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/5c7340e80289
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-12-23 13:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 12:51 [PATCH mptcp-next 0/3] mptcp: add support for mixed v4/v6 Paolo Abeni
2022-12-23 12:51 ` [PATCH mptcp-next 1/3] mptcp: explicitly specify sock family at subflow creation time Paolo Abeni
2022-12-23 14:35 ` Matthieu Baerts
2022-12-23 16:01 ` Paolo Abeni
2022-12-23 16:08 ` Matthieu Baerts
2022-12-23 18:32 ` Paolo Abeni
2022-12-23 12:51 ` [PATCH mptcp-next 2/3] mptcp: let the in kernel PM use mixed ipv4 and ipv6 addresses Paolo Abeni
2022-12-23 14:35 ` Matthieu Baerts
2022-12-23 18:31 ` Paolo Abeni
2022-12-23 12:51 ` [PATCH mptcp-next 3/3] selftests: mptcp: add test-cases for mixed v4/v6 subflows Paolo Abeni
2022-12-23 13:58 ` MPTCP CI [this message]
2022-12-23 14:35 ` Matthieu Baerts
2022-12-23 18:29 ` Paolo Abeni
2022-12-26 13:09 ` Matthieu Baerts
2022-12-26 13:16 ` Matthieu Baerts
2022-12-23 14:35 ` [PATCH mptcp-next 0/3] mptcp: add support for mixed v4/v6 Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2022-12-23 19:00 [PATCH v2 mptcp-next 3/3] selftests: mptcp: add test-cases for mixed v4/v6 subflows Paolo Abeni
2022-12-23 19:37 ` selftests: mptcp: add test-cases for mixed v4/v6 subflows: 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=2cdb8605-6f9d-2298-bbe4-c55afe2cabdb@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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