From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.com>, netdev@vger.kernel.org
Subject: [TEST] net/bind_wildcard flakiness
Date: Fri, 16 May 2025 10:05:42 -0700 [thread overview]
Message-ID: <20250516100542.67c276ec@kernel.org> (raw)
Hi!
The bind_wildcard used to be rock solid, no flakes in last 1000 runs,
but then around the time Eric posted his Rx optimizations we hit one
flake, and now we hit another:
List:
https://netdev.bots.linux.dev/contest.html?test=bind-wildcard&executor=vmksft-net&pass=0
Outputs:
https://netdev-3.bots.linux.dev/vmksft-net/results/122022/14-bind-wildcard/stdout
https://netdev-3.bots.linux.dev/vmksft-net/results/123463/14-bind-wildcard/stdout
One does:
# 0.21 [+0.00] # bind_wildcard.c:768:reuseaddr:Expected ret (-1) == 0 (0)
# 0.21 [+0.00] # reuseaddr: Test terminated by assertion
# 0.21 [+0.00] # FAIL bind_wildcard.v6_any_only_v6_v4mapped_any.reuseaddr
The other:
# 0.25 [+0.00] # bind_wildcard.c:775:plain:Expected ret (-1) == 0 (0)
# 0.25 [+0.00] # plain: Test terminated by assertion
# 0.25 [+0.00] # FAIL bind_wildcard.v6_local_v6_v4mapped_any.plain
The only change on the infra side is that I increased disk IO cap,
so the builds are now faster.
next reply other threads:[~2025-05-16 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 17:05 Jakub Kicinski [this message]
2025-05-16 17:44 ` [TEST] net/bind_wildcard flakiness Kuniyuki Iwashima
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=20250516100542.67c276ec@kernel.org \
--to=kuba@kernel.org \
--cc=kuniyu@amazon.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).