From: Jakub Kicinski <kuba@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org
Subject: [TEST] bond_macvlan_ipvlan.sh flakiness
Date: Fri, 14 Nov 2025 08:20:14 -0800 [thread overview]
Message-ID: <20251114082014.750edfad@kernel.org> (raw)
Hi Hangbin!
The flakiness of bond_macvlan_ipvlan.sh has increased quite a lot
recently. Not sure if there's any correlation with kernel changes,
I didn't spot anything in bonding itself. Here's the history of runs:
https://netdev.bots.linux.dev/contest.html?executor=vmksft-bonding&test=bond-macvlan-ipvlan-sh
It looks like it's gotten much worse starting around the 9th?
Only the non-debug kernel build is flaking, debug builds are completely
clear:
https://netdev.bots.linux.dev/flakes.html?min-flip=0&tn-needle=bond-macvlan-ipvlan-sh
A few things that stood out to me, all the failures are like this:
# TEST: balance-$lb/$$$vlan_bridge: IPv4: client->$$$vlan_2 [FAIL]
Always IPv4 ping to the second interface, always fails neighbor
resolution:
# 192.0.2.12 dev eth0 FAILED
If it's ipvlan that fails rather than macvlan there is a bunch of
otherhost drops:
# 17: ipvlan0@if15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
# link/ether 00:0a:0b:0c:0d:01 brd ff:ff:ff:ff:ff:ff link-netns s-8BLcCn
# RX: bytes packets errors dropped missed mcast
# 702 10 0 0 0 3
# RX errors: length crc frame fifo overrun otherhost
# 0 0 0 0 0 4
FWIW here's the contents of the branches if you want to look thru:
https://netdev.bots.linux.dev/static/nipa/branch_deltas/net-next-2025-11-09--12-00.html
but 9th was the weekend, and the failure just got more frequent,
we've been trying to track this down for a while..
next reply other threads:[~2025-11-14 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 16:20 Jakub Kicinski [this message]
2025-11-17 8:24 ` [TEST] bond_macvlan_ipvlan.sh flakiness Hangbin Liu
2025-11-18 6:03 ` Hangbin Liu
2025-11-18 15:13 ` Jakub Kicinski
2025-11-26 15:19 ` Jakub Kicinski
2025-11-27 1:14 ` Hangbin Liu
2025-11-27 1:18 ` Hangbin Liu
2025-11-27 1:41 ` Jakub Kicinski
2025-11-27 2:04 ` Hangbin Liu
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=20251114082014.750edfad@kernel.org \
--to=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).