From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Safonov <0x7f454c46@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [TEST] tcp-ao/connect-deny-ipv6 is flaky
Date: Thu, 5 Dec 2024 07:06:56 -0800 [thread overview]
Message-ID: <20241205070656.6ef344d7@kernel.org> (raw)
Hi Dmitry!
Looks like around Nov 14th TCP AO connect-deny-ipv6 test has gotten
quite flaky. See:
https://netdev.bots.linux.dev/contest.html?test=connect-deny-ipv6
Spot checking a few looks like the failures are on test case 22:
# # 325[lib/ftrace-tcp.c:427] trace event filter tcp_ao_key_not_found [2001:db8:1::1:-1 => 2001:db8:254::1:7010, L3index 0, flags: !FS!R!P!., keyid: 100, rnext: 100, maclen: -1, sne: -1] = 0
# # 325[lib/ftrace-tcp.c:427] trace event filter tcp_hash_ao_required [2001:db8:1::1:-1 => 2001:db8:254::1:7011, L3index 0, flags: !FS!R!P!., keyid: -1, rnext: -1, maclen: -1, sne: -1] = 1
# # 325[lib/ftrace-tcp.c:427] trace event filter tcp_ao_mismatch [2001:db8:1::1:-1 => 2001:db8:254::1:7012, L3index 0, flags: !FS!R!P!., keyid: 100, rnext: 100, maclen: -1, sne: -1] = 1
# # 325[lib/ftrace-tcp.c:427] trace event filter tcp_ao_key_not_found [2001:db8:1::1:-1 => 2001:db8:254::1:7013, L3index 0, flags: !FS!R!P!., keyid: 100, rnext: 100, maclen: -1, sne: -1] = 1
# # 325[lib/ftrace-tcp.c:427] trace event filter tcp_ao_synack_no_key [2001:db8:254::1:7014 => :::0, L3index -1, flags: , keyid: 100, rnext: 100, maclen: -1, sne: -1] = 1
# # 325[lib/ftrace-tcp.c:427] trace event filter tcp_ao_wrong_maclen [2001:db8:1::1:-1 => 2001:db8:254::1:7015, L3index 0, flags: !FS!R!P!., keyid: 100, rnext: 100, maclen: -1, sne: -1] = 1
# # 325[lib/ftrace-tcp.c:427] trace event filter tcp_ao_key_not_found [2001:db8:1::1:-1 => 2001:db8:254::1:7016, L3index 0, flags: !FS!R!P!., keyid: 100, rnext: 100, maclen: -1, sne: -1] = 1
# not ok 22 Some trace events were expected, but didn't occur
Nothing looks obviously relevant in:
git log --oneline --since='Nov 14' --until='Nov 18'
I have installed virtiofsd on the test setup around Nov 9th (which
speeds up tests) but that also doesn't align very well..
I'll filter that test out of our CI for now, please TAL when you have
time.
next reply other threads:[~2024-12-05 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 15:06 Jakub Kicinski [this message]
2024-12-06 0:28 ` [TEST] tcp-ao/connect-deny-ipv6 is flaky Dmitry Safonov
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=20241205070656.6ef344d7@kernel.org \
--to=kuba@kernel.org \
--cc=0x7f454c46@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).