From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
shuah@kernel.org, petrm@nvidia.com, leitao@debian.org,
noren@nvidia.com, gal@nvidia.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: net: py: give bpftrace more time to start
Date: Tue, 17 Mar 2026 02:30:10 +0000 [thread overview]
Message-ID: <177371461053.3397946.6102878609227085799.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260315160038.3187730-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 15 Mar 2026 09:00:38 -0700 you wrote:
> After commit under Fixes debug runners in the CI hit the following:
>
> # subprocess.TimeoutExpired: Command '['bpftrace', '-f', 'json', '-q', '-e', 'kprobe:netpoll_poll_dev { @hits = count(); } interval:s:10 { exit(); }']' timed out after 15 seconds
> # # Exception| net.lib.py.ksft.KsftFailEx: bpftrace failed to run!?: {}
>
> in netpoll_basic.py >10% of the time. Let's give bpftool more time
> to start, it can take a while on a debug kernel.
>
> [...]
Here is the summary with links:
- [net-next] selftests: net: py: give bpftrace more time to start
https://git.kernel.org/netdev/net-next/c/6a33a706265d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-17 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 16:00 [PATCH net-next] selftests: net: py: give bpftrace more time to start Jakub Kicinski
2026-03-16 9:05 ` Breno Leitao
2026-03-16 9:33 ` Petr Machata
2026-03-16 15:25 ` Nimrod Oren
2026-03-17 2:30 ` patchwork-bot+netdevbpf [this message]
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=177371461053.3397946.6102878609227085799.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
/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