From: Ido Schimmel <idosch@nvidia.com>
To: <netdev@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>,
<edumazet@google.com>, <shuah@kernel.org>, <petrm@nvidia.com>,
<razor@blackwall.org>, <liuhangbin@gmail.com>,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net 0/4] selftests: forwarding: Various fixes
Date: Thu, 8 Feb 2024 17:55:25 +0200 [thread overview]
Message-ID: <20240208155529.1199729-1-idosch@nvidia.com> (raw)
Fix various problems in the forwarding selftests so that they will pass
in the netdev CI instead of being ignored. See commit messages for
details.
Ido Schimmel (4):
selftests: forwarding: Fix layer 2 miss test flakiness
selftests: forwarding: Fix bridge MDB test flakiness
selftests: forwarding: Suppress grep warnings
selftests: forwarding: Fix bridge locked port test flakiness
.../selftests/net/forwarding/bridge_locked_port.sh | 4 ++--
.../testing/selftests/net/forwarding/bridge_mdb.sh | 14 +++++++++-----
.../selftests/net/forwarding/tc_flower_l2_miss.sh | 8 ++++++--
3 files changed, 17 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-08 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 15:55 Ido Schimmel [this message]
2024-02-08 15:55 ` [PATCH net 1/4] selftests: forwarding: Fix layer 2 miss test flakiness Ido Schimmel
2024-02-08 15:55 ` [PATCH net 2/4] selftests: forwarding: Fix bridge MDB " Ido Schimmel
2024-02-08 15:55 ` [PATCH net 3/4] selftests: forwarding: Suppress grep warnings Ido Schimmel
2024-02-08 15:55 ` [PATCH net 4/4] selftests: forwarding: Fix bridge locked port test flakiness Ido Schimmel
2024-02-09 8:56 ` [PATCH net 0/4] selftests: forwarding: Various fixes Hangbin Liu
2024-02-09 10:39 ` Nikolay Aleksandrov
2024-02-09 19:40 ` patchwork-bot+netdevbpf
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=20240208155529.1199729-1-idosch@nvidia.com \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--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