From: Jakub Kicinski <kuba@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>, Hangbin Liu <liuhangbin@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [TEST] test_bridge_neigh_suppress.sh now failing in both configs
Date: Fri, 26 Apr 2024 07:40:15 -0700 [thread overview]
Message-ID: <20240426074015.251854d4@kernel.org> (raw)
Hi Ido, Hangbin Liu,
test_bridge_neigh_suppress.sh has always been failing on debug kernels:
# Per-port ARP suppression - VLAN 10
# ----------------------------------
# TEST: arping [FAIL]
# TEST: ARP suppression [ OK ]
# TEST: "neigh_suppress" is on [ OK ]
# TEST: arping [FAIL]
# TEST: ARP suppression [ OK ]
# TEST: FDB entry installation [ OK ]
# TEST: arping [FAIL]
# TEST: ARP suppression [ OK ]
# TEST: Neighbor entry installation [ OK ]
# TEST: arping [FAIL]
# TEST: ARP suppression [ OK ]
# TEST: H2 down [ OK ]
# TEST: arping [FAIL]
...
after we forwarded the trees to Linus's branch on Thu it's now also
failing on non-debug kernel, in the same way. It fails every time
for us, so should be easy to repro. If you find some spare cycles,
could you take a look?
next reply other threads:[~2024-04-26 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 14:40 Jakub Kicinski [this message]
2024-04-30 10:57 ` [TEST] test_bridge_neigh_suppress.sh now failing in both configs Ido Schimmel
2024-05-01 1:08 ` Jakub Kicinski
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=20240426074015.251854d4@kernel.org \
--to=kuba@kernel.org \
--cc=idosch@nvidia.com \
--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 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.