From: Jakub Kicinski <kuba@kernel.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [TEST] conntrack_reverse_clash.sh flakes
Date: Sat, 6 Dec 2025 17:56:47 -0800 [thread overview]
Message-ID: <20251206175647.5c32f419@kernel.org> (raw)
In-Reply-To: <20251206175135.4a56591b@kernel.org>
On Sat, 6 Dec 2025 17:51:35 -0800 Jakub Kicinski wrote:
> Hi Florian!
>
> We have a new faster NIPA setup, and now on non-debug builds we see
> a few (4 a week to be exact) flakes in conntrack_reverse_clash.sh
Ah, one more, the non-reverse conntrack-clash is SKIPping, occasionally:
https://netdev.bots.linux.dev/contest.html?pass=0&test=conntrack-clash-sh
If the event it's testing is probabilistic could we make it return XFAIL
when it doesn't trigger? We try to reserve SKIP for tests skipped
because tool is missing in env, something isn't built into the kernel
etc.
next prev parent reply other threads:[~2025-12-07 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-07 1:51 [TEST] conntrack_reverse_clash.sh flakes Jakub Kicinski
2025-12-07 1:56 ` Jakub Kicinski [this message]
2025-12-07 10:40 ` Florian Westphal
2025-12-08 14:48 ` Florian Westphal
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=20251206175647.5c32f419@kernel.org \
--to=kuba@kernel.org \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).