From: Jakub Kicinski <kuba@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>
Cc: Hangbin Liu <liuhangbin@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [TEST] test_bridge_neigh_suppress.sh now failing in both configs
Date: Tue, 30 Apr 2024 18:08:47 -0700 [thread overview]
Message-ID: <20240430180847.43ff7c63@kernel.org> (raw)
In-Reply-To: <ZjDOn9SNq8baOfZB@shredder>
On Tue, 30 Apr 2024 13:57:35 +0300 Ido Schimmel wrote:
> On Fri, Apr 26, 2024 at 07:40:15AM -0700, Jakub Kicinski wrote:
> > 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?
>
> Will check
Thanks, FWIW I just noticed that vxlan_bridge_1d.sh suffered
similar fate, although in that case it's the debug flavor
that started to fail.
prev parent reply other threads:[~2024-05-01 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 14:40 [TEST] test_bridge_neigh_suppress.sh now failing in both configs Jakub Kicinski
2024-04-30 10:57 ` Ido Schimmel
2024-05-01 1:08 ` Jakub Kicinski [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=20240430180847.43ff7c63@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 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).