From: Jakub Kicinski <kuba@kernel.org>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [TEST] forwarding: bridge_mld.sh flaky after the merge window
Date: Fri, 4 Oct 2024 12:11:16 -0700 [thread overview]
Message-ID: <20241004121116.1b9a2e5e@kernel.org> (raw)
Hi Nik!
Looks like bridge_mld.sh got a little bit flaky after we pulled the
6.12 merge window material (I'm just guessing it's the merge window
because it seems to have started last Thu after forwarding our trees):
# 240.89 [+21.95] TEST: MLDv2 group ff02::cc exclude timeout [FAIL]
# 240.89 [+0.00] Entry 2001:db8:1::2 has zero timer succeeded, but should have failed
https://netdev.bots.linux.dev/flakes.html?min-flip=0&tn-needle=bridge-mld-sh
https://netdev.bots.linux.dev/contest.html?executor=vmksft-forwarding-dbg&test=bridge-mld-sh
next reply other threads:[~2024-10-04 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 19:11 Jakub Kicinski [this message]
2024-10-04 19:12 ` [TEST] forwarding: bridge_mld.sh flaky after the merge window Jakub Kicinski
2024-10-05 14:11 ` Nikolay Aleksandrov
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=20241004121116.1b9a2e5e@kernel.org \
--to=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.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).