From: Jakub Kicinski <kuba@kernel.org>
To: Petr Machata <petrm@nvidia.com>, netdev@vger.kernel.org
Subject: [TEST] vxlan brige test flakiness
Date: Wed, 3 Dec 2025 09:50:55 -0800 [thread overview]
Message-ID: <20251203095055.3718f079@kernel.org> (raw)
Hi!
We're seeing a few more flakes on vxlan-bridge-1q-mc-ul-sh and
vxlan-bridge-1q-mc-ul-sh in the new setup than we used to (tho
the former was always relatively flaky).
# 141.78 [+13.13] TEST: VXLAN MC flood IPv6 mcroute changelink [FAIL]
# 141.78 [+0.00] Expected 10 packets on H2, got 11
# 141.83 [+0.04] smcroutectl: mroute: deleting route from lo10 (192.0.2.33/32,233.252.0.1/32)
https://netdev.bots.linux.dev/contest.html?pass=0&executor=vmksft-forwarding&test=vxlan-bridge-1q-mc-ul-sh&pw-n=0
Perhaps we should make the filter more specific to the test traffic?
LMK if you need access to the system.
next reply other threads:[~2025-12-03 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 17:50 Jakub Kicinski [this message]
2025-12-04 17:46 ` [TEST] vxlan brige test flakiness Petr Machata
2025-12-04 18:43 ` Jakub Kicinski
2025-12-05 16:16 ` Petr Machata
2025-12-06 0:26 ` Jakub Kicinski
2025-12-08 10:27 ` Petr Machata
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=20251203095055.3718f079@kernel.org \
--to=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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 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).