From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: Add struct mptcp_sock definition when CONFIG_MPTCP is disabled: Tests Results
Date: Mon, 11 Jul 2022 14:41:08 +0000 [thread overview]
Message-ID: <c65825b7-2d9c-4f49-ee75-426d7d59c50e@gmail.com> (raw)
In-Reply-To: <20220711130731.3231188-1-jolsa@kernel.org>
Hi Jiri,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- KVM Validation: normal:
- Unstable: 2 failed test(s): selftest_mptcp_join selftest_simult_flows 🔴:
- Task: https://cirrus-ci.com/task/5307521400307712
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5307521400307712/summary/summary.txt
- KVM Validation: debug:
- Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
- Task: https://cirrus-ci.com/task/6433421307150336
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6433421307150336/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/1d9ed6cb0b33
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-07-11 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 13:07 [PATCH bpf-next] mptcp: Add struct mptcp_sock definition when CONFIG_MPTCP is disabled Jiri Olsa
2022-07-11 14:41 ` MPTCP CI [this message]
2022-07-11 20:27 ` Martin KaFai Lau
2022-07-11 21:21 ` Mat Martineau
2022-07-12 9:06 ` Matthieu Baerts
2022-07-12 12:12 ` Jiri Olsa
2022-07-12 13:06 ` Matthieu Baerts
2022-07-12 17:05 ` Mat Martineau
-- strict thread matches above, loose matches on Subject: below --
2022-08-02 16:33 [PATCHv2 " Jiri Olsa
2022-08-02 19:16 ` mptcp: Add struct mptcp_sock definition when CONFIG_MPTCP is disabled: Tests Results MPTCP CI
2022-08-03 18:07 ` 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=c65825b7-2d9c-4f49-ee75-426d7d59c50e@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=jolsa@kernel.org \
--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