From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: udp: track the forward memory release threshold in an hot cacheline: Tests Results
Date: Thu, 20 Oct 2022 21:14:15 +0000 [thread overview]
Message-ID: <796796d4-883e-1489-eace-2884ed20fa0d@gmail.com> (raw)
In-Reply-To: <2dede94e742d8096d6ac5e0f1979054ee158d9a8.1666287924.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:
- Success! ✅:
- Task: https://cirrus-ci.com/task/5317274872578048
- Summary: https://api.cirrus-ci.com/v1/artifact/task/5317274872578048/summary/summary.txt
- {"code":404,"message":
- "Can't find artifacts containing file conclusion.txt"}:
- Task: https://cirrus-ci.com/task/6443174779420672
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6443174779420672/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/31ed4dad9833
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-10-20 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 17:48 [PATCH net-next v2 0/2] udp: avoid false sharing on receive Paolo Abeni
2022-10-20 17:48 ` [PATCH net-next v2 1/2] net: introduce and use custom sockopt socket flag Paolo Abeni
2022-10-20 18:11 ` Eric Dumazet
2022-10-20 18:19 ` Kuniyuki Iwashima
2022-10-20 17:48 ` [PATCH net-next v2 2/2] udp: track the forward memory release threshold in an hot cacheline Paolo Abeni
2022-10-20 18:10 ` Eric Dumazet
2022-10-20 18:20 ` Kuniyuki Iwashima
2022-10-20 21:14 ` MPTCP CI [this message]
2022-10-24 10:30 ` [PATCH net-next v2 0/2] udp: avoid false sharing on receive patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2022-10-19 10:02 [PATCH net-next 2/2] udp: track the forward memory release threshold in an hot cacheline Paolo Abeni
2022-10-19 12:03 ` udp: track the forward memory release threshold in an hot cacheline: Tests Results MPTCP CI
2022-10-19 17:16 ` 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=796796d4-883e-1489-eace-2884ed20fa0d@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