From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, sohamch@google.com,
willemb@google.com
Subject: Re: [PATCH net-next] selftests/net: packetdrill: report benign debug flakes as xfail
Date: Tue, 07 Jan 2025 10:30:32 +0000 [thread overview]
Message-ID: <173624583226.4099602.7245527834877718325.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250103113142.129251-1-willemdebruijn.kernel@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 3 Jan 2025 06:31:14 -0500 you wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> A few recently added packetdrill tests that are known time sensitive
> (e.g., because testing timestamping) occasionally fail in debug mode:
> https://netdev.bots.linux.dev/contest.html?executor=vmksft-packetdrill-dbg
>
> These failures are well understood. Correctness of the tests is
> verified in non-debug mode. Continue running in debug mode also, to
> keep coverage with debug instrumentation.
>
> [...]
Here is the summary with links:
- [net-next] selftests/net: packetdrill: report benign debug flakes as xfail
https://git.kernel.org/netdev/net-next/c/912d6f669725
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-01-07 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 11:31 [PATCH net-next] selftests/net: packetdrill: report benign debug flakes as xfail Willem de Bruijn
2025-01-07 10: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=173624583226.4099602.7245527834877718325.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=sohamch@google.com \
--cc=willemb@google.com \
--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