From: Jakub Kicinski <kuba@kernel.org>
To: Petr Machata <petrm@nvidia.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [TEST] vxlan brige test flakiness
Date: Thu, 4 Dec 2025 10:43:37 -0800 [thread overview]
Message-ID: <20251204104337.7edf0a31@kernel.org> (raw)
In-Reply-To: <87bjkexhhr.fsf@nvidia.com>
On Thu, 4 Dec 2025 18:46:30 +0100 Petr Machata wrote:
> Jakub Kicinski <kuba@kernel.org> writes:
> > 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).
>
> You listed the same test twice, so that's the one that I'm looking into now.
Ah, I thought one of them was 1d but indeed the CI was just reporting
it twice because of different machine running the test. It's just one
test case that's flaking on two setups.
next prev parent reply other threads:[~2025-12-04 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 17:50 [TEST] vxlan brige test flakiness Jakub Kicinski
2025-12-04 17:46 ` Petr Machata
2025-12-04 18:43 ` Jakub Kicinski [this message]
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=20251204104337.7edf0a31@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).