From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, andrew+netdev@lunn.ch,
petrm@nvidia.com
Subject: Re: [PATCH net] selftests: netdevsim: Xfail nexthop test on slow machines
Date: Tue, 05 Aug 2025 23:50:06 +0000 [thread overview]
Message-ID: <175443780651.2205590.13469597711317035634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250804114320.193203-1-idosch@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 4 Aug 2025 14:43:20 +0300 you wrote:
> A lot of test cases in the file are related to the idle and unbalanced
> timers of resilient nexthop groups and these tests are reported to be
> flaky on slow machines running debug kernels.
>
> Rather than marking a lot of individual tests with xfail_on_slow(),
> simply mark all the tests. Note that the test is stable on non-debug
> machines and that with debug kernels we are mainly interested in the
> output of various sanitizers in order to determine pass / fail.
>
> [...]
Here is the summary with links:
- [net] selftests: netdevsim: Xfail nexthop test on slow machines
https://git.kernel.org/netdev/net/c/8d22aea8af0d
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:[~2025-08-05 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 11:43 [PATCH net] selftests: netdevsim: Xfail nexthop test on slow machines Ido Schimmel
2025-08-05 23:50 ` 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=175443780651.2205590.13469597711317035634.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=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.