From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: userspace: avoid read errors: Tests Results
Date: Thu, 05 Jan 2023 08:32:43 +0000 [thread overview]
Message-ID: <8a778ab4-18dd-e342-bbe3-5154cf82ee72@gmail.com> (raw)
In-Reply-To: <20230104171526.1416746-13-matthieu.baerts@tessares.net>
Hi Matthieu,
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/6007793140891648
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6007793140891648/summary/summary.txt
- KVM Validation: normal (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/5444843187470336
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5444843187470336/summary/summary.txt
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6570743094312960
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6570743094312960/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
- Task: https://cirrus-ci.com/task/4741155745693696
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4741155745693696/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/b224e1e9ab22
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:[~2023-01-05 8:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 17:15 [PATCH mptcp-net/next v5 00/12] mptcp: add support for mixed v4/v6 Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-net v5 01/12] mptcp: explicitly specify sock family at subflow creation time Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-net v5 02/12] mptcp: netlink: respect v4/v6-only sockets Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-net v5 03/12] selftests: mptcp: userspace: validate v4-v6 subflows mix Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 04/12] mptcp: let the in-kernel PM use mixed IPv4 and IPv6 addresses Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 05/12] mptcp: propagate sk_ipv6only to subflows Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 06/12] selftests: mptcp: add test-cases for mixed v4/v6 subflows Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 07/12] mptcp: remove assigned but unused value Matthieu Baerts
2023-01-10 9:20 ` Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 08/12] mptcp: userspace pm: use a single point of exit Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 09/12] selftests: mptcp: userspace: print titles Matthieu Baerts
2023-01-06 1:19 ` Mat Martineau
2023-01-06 6:34 ` Matthieu Baerts
2023-01-06 16:34 ` Mat Martineau
2023-01-04 17:15 ` [PATCH mptcp-next v5 10/12] selftests: mptcp: userspace: refactor asserts Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 11/12] selftests: mptcp: userspace: print error details if any Matthieu Baerts
2023-01-04 17:15 ` [PATCH mptcp-next v5 12/12] selftests: mptcp: userspace: avoid read errors Matthieu Baerts
2023-01-05 8:32 ` MPTCP CI [this message]
2023-01-06 2:39 ` selftests: mptcp: userspace: avoid read errors: Tests Results MPTCP CI
2023-01-06 17:39 ` MPTCP CI
2023-01-06 1:15 ` [PATCH mptcp-net/next v5 00/12] mptcp: add support for mixed v4/v6 Mat Martineau
2023-01-09 17:04 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2022-12-28 10:17 [PATCH mptcp-next v4 12/12] selftests: mptcp: userspace: avoid read errors Matthieu Baerts
2022-12-28 16:13 ` selftests: mptcp: userspace: avoid read errors: 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=8a778ab4-18dd-e342-bbe3-5154cf82ee72@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=matthieu.baerts@tessares.net \
--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 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.