From: Jakub Kicinski <kuba@kernel.org>
To: Petr Machata <petrm@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Hangbin Liu <liuhangbin@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [TEST] forwarding/router_bridge_lag.sh started to flake on Monday
Date: Thu, 22 Aug 2024 08:37:18 -0700 [thread overview]
Message-ID: <20240822083718.140e9e65@kernel.org> (raw)
Hi!
Looks like forwarding/router_bridge_lag.sh has gotten a lot more flaky
this week. It flaked very occasionally (and in a different way) before:
https://netdev.bots.linux.dev/contest.html?executor=vmksft-forwarding&test=router-bridge-lag-sh&ld_cnt=250
There doesn't seem to be any obvious commit that could have caused this.
Any ideas?
next reply other threads:[~2024-08-22 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 15:37 Jakub Kicinski [this message]
2024-08-23 11:28 ` [TEST] forwarding/router_bridge_lag.sh started to flake on Monday Petr Machata
2024-08-23 15:02 ` Jakub Kicinski
2024-08-23 16:13 ` Petr Machata
2024-08-24 21:27 ` Jakub Kicinski
2024-08-25 9:01 ` 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=20240822083718.140e9e65@kernel.org \
--to=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--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).