From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: mptcp: annotate lockless accesses around read-mostly fields: Tests Results
Date: Tue, 23 Jan 2024 02:52:31 +0000 [thread overview]
Message-ID: <ada09308-4902-24fa-432c-eefaf72e27f0@gmail.com> (raw)
In-Reply-To: <4f4ba04c46b432b5f2a95bb75d85912bcb937cfb.1705427537.git.pabeni@redhat.com>
Hi Paolo,
Thank you for your modifications, that's great!
Our CI (Cirrus) did some validations with a debug kernel and here is its report:
- KVM Validation: debug (except selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/6203989608366080
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6203989608366080/summary/summary.txt
- KVM Validation: debug (only selftest_mptcp_join):
- Success! ✅:
- Task: https://cirrus-ci.com/task/4796614724812800
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4796614724812800/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/8a9166777803
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 (NGI0 Core)
next prev parent reply other threads:[~2024-01-23 2:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 18:16 [PATCH mptcp-next 0/5] mptcp: annotate lockless access Paolo Abeni
2024-01-16 18:16 ` [PATCH mptcp-next 1/5] mptcp: annotate access for msk keys Paolo Abeni
2024-01-16 18:16 ` [PATCH mptcp-next 2/5] mptcp: annotate lockless access for the tx path Paolo Abeni
2024-01-19 1:03 ` Mat Martineau
2024-01-21 21:47 ` Paolo Abeni
2024-01-22 15:07 ` Paolo Abeni
2024-01-23 1:21 ` Mat Martineau
2024-01-16 18:16 ` [PATCH mptcp-next 3/5] mptcp: annotate lockless access for RX path fields Paolo Abeni
2024-01-16 18:16 ` [PATCH mptcp-next 4/5] mptcp: annotate lockless access for token Paolo Abeni
2024-01-16 18:16 ` [PATCH mptcp-next 5/5] mptcp: annotate lockless accesses around read-mostly fields Paolo Abeni
2024-01-17 17:48 ` mptcp: annotate lockless accesses around read-mostly fields: Tests Results MPTCP CI
2024-01-17 18:38 ` MPTCP CI
2024-01-23 2:33 ` MPTCP CI
2024-01-23 2:52 ` MPTCP CI [this message]
2024-01-23 1:21 ` [PATCH mptcp-next 0/5] mptcp: annotate lockless access Mat Martineau
2024-01-30 12:19 ` 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=ada09308-4902-24fa-432c-eefaf72e27f0@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