From: Breno Leitao <leitao@debian.org>
To: Mat Martineau <martineau@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results
Date: Mon, 22 May 2023 04:17:43 -0700 [thread overview]
Message-ID: <ZGtPV9VvAhqDXk8e@gmail.com> (raw)
In-Reply-To: <7f3ef790-1cca-5cea-46f8-3aa838da59b7@kernel.org>
On Fri, May 19, 2023 at 11:03:04AM -0700, Mat Martineau wrote:
> On Fri, 19 May 2023, MPTCP CI wrote:
>
> > Hi Breno,
> >
> > 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):
> > - Unstable: 1 failed test(s): packetdrill_fastopen 🔴:
> > - Task: https://cirrus-ci.com/task/6416256383844352
> > - Summary: https://api.cirrus-ci.com/v1/artifact/task/6416256383844352/summary/summary.txt
> >
> > - KVM Validation: normal (only selftest_mptcp_join):
> > - Success! ✅:
> > - Task: https://cirrus-ci.com/task/5008881500291072
> > - Summary: https://api.cirrus-ci.com/v1/artifact/task/5008881500291072/summary/summary.txt
> >
> > - KVM Validation: debug (except selftest_mptcp_join):
> > - Unstable: 6 failed test(s): packetdrill_add_addr packetdrill_dss packetdrill_fastopen packetdrill_mp_capable packetdrill_sockopts selftest_diag 🔴:
> > - Task: https://cirrus-ci.com/task/6134781407133696
> > - Summary: https://api.cirrus-ci.com/v1/artifact/task/6134781407133696/summary/summary.txt
>
> Hi Breno -
>
> These appear to be false positives that are popping up in our CI on other
> patches too, no need for you to check on them!
Thanks for the heads-up!
next prev parent reply other threads:[~2023-05-22 11:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 13:58 [PATCH 0/1] net: ioctl: Use kernel buffer on proto ioctl callbacks Breno Leitao
2023-05-19 13:58 ` [PATCH 1/1] net: ioctl: Use kernel memory on protocol " Breno Leitao
2023-05-19 14:22 ` David Laight
2023-05-19 15:09 ` Willem de Bruijn
2023-05-19 15:39 ` Breno Leitao
2023-05-19 17:04 ` Willem de Bruijn
2023-05-20 12:48 ` David Laight
2023-05-20 13:02 ` David Laight
2023-05-19 15:25 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-05-19 18:03 ` Mat Martineau
2023-05-22 11:17 ` Breno Leitao [this message]
2023-05-19 16:54 ` [PATCH 1/1] net: ioctl: Use kernel memory on protocol ioctl callbacks kernel test robot
2023-05-19 19:26 ` kernel test robot
2023-05-19 23:29 ` kernel test robot
2023-05-20 3:50 ` David Ahern
2023-05-19 15:15 ` [PATCH 0/1] net: ioctl: Use kernel buffer on proto " Jakub Kicinski
2023-05-19 15:19 ` Breno Leitao
-- strict thread matches above, loose matches on Subject: below --
2023-05-22 13:47 [PATCH v2] net: ioctl: Use kernel memory on protocol " Breno Leitao
2023-05-22 17:11 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-05-25 12:54 [PATCH net-next v3] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-05-25 15:16 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-05-30 17:53 [PATCH net-next v4] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-05-30 19:38 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-06-02 16:30 [PATCH net-next v5] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-06-02 18:03 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-06-06 18:00 [PATCH net-next v6] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-06-06 19:09 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-06-07 13:25 ` MPTCP CI
2023-06-07 15:57 ` MPTCP CI
2023-06-09 15:27 [PATCH net-next v7] net: ioctl: Use kernel memory on protocol ioctl callbacks Breno Leitao
2023-06-09 17:37 ` net: ioctl: Use kernel memory on protocol ioctl callbacks: Tests Results MPTCP CI
2023-06-09 21:01 ` 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=ZGtPV9VvAhqDXk8e@gmail.com \
--to=leitao@debian.org \
--cc=martineau@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