From: Breno Leitao <leitao@debian.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org
Subject: Re: [PATCH net-next v3 3/3] selftests: net: add netpoll basic functionality test
Date: Mon, 30 Jun 2025 10:30:13 -0700 [thread overview]
Message-ID: <aGLJpaNLPYnPwKYV@gmail.com> (raw)
In-Reply-To: <20250627113854.04c13ace@kernel.org>
On Fri, Jun 27, 2025 at 11:38:54AM -0700, Jakub Kicinski wrote:
> On Fri, 27 Jun 2025 10:03:11 -0700 Breno Leitao wrote:
> > + raise KsftSkipEx("netpoll_poll_dev() was not called. Skipping test")
>
> As discussed offline SKIPing is not an option for SW tests.
Sure, I will move it to failure.
Unfortunately the expected path didn't hit in vmtest. I am still trying
to reproduce the failure on my side, but no luck. It hits from 10 to 16
times per run.
Do you want me to send it as a failure, or, wait until we get something
better that pass 100% of the time?
Thanks
--breno
next prev parent reply other threads:[~2025-06-30 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 17:03 [PATCH net-next v3 0/3] selftest: net: Add selftest for netpoll Breno Leitao
2025-06-27 17:03 ` [PATCH net-next v3 1/3] selftests: drv-net: add helper/wrapper for bpftrace Breno Leitao
2025-06-27 17:03 ` [PATCH net-next v3 2/3] selftests: drv-net: Strip '@' prefix from bpftrace map keys Breno Leitao
2025-06-27 17:03 ` [PATCH net-next v3 3/3] selftests: net: add netpoll basic functionality test Breno Leitao
2025-06-27 18:38 ` Jakub Kicinski
2025-06-30 17:30 ` Breno Leitao [this message]
2025-06-28 14:57 ` Willem de Bruijn
2025-06-30 14:32 ` Breno Leitao
2025-06-30 17:53 ` Willem de Bruijn
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=aGLJpaNLPYnPwKYV@gmail.com \
--to=leitao@debian.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemdebruijn.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).