[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aHj0QSJkzexEKE2T@strlen.de>
Date: Thu, 17 Jul 2025 15:01:53 +0200
From: Florian Westphal <fw@...len.de>
To: Paolo Abeni <pabeni@...hat.com>
Cc: Pablo Neira Ayuso <pablo@...filter.org>,
netfilter-devel@...r.kernel.org, davem@...emloft.net,
netdev@...r.kernel.org, kuba@...nel.org, edumazet@...gle.com,
horms@...nel.org
Subject: Re: [PATCH net,v2 0/7] Netfilter fixes for net
Paolo Abeni <pabeni@...hat.com> wrote:
> The first run of the newly introduced conntrack_clash.sh test failed on
> nipa:
>
> # timeout set to 1800
> # selftests: net/netfilter: conntrack_clash.sh
> # got 128 of 128 replies
> # timed out while waiting for reply from thread
> # got 127 of 128 replies
> # FAIL: did not receive expected number of replies for 10.0.1.99:22111
> # FAIL: clash resolution test for 10.0.1.99:22111 on attempt 2
> # got 128 of 128 replies
> # timed out while waiting for reply from thread
> # got 0 of 128 replies
> # FAIL: did not receive expected number of replies for 127.0.0.1:9001
> # FAIL: clash resolution test for 127.0.0.1:9001 on attempt 2
> # SKIP: Clash resolution did not trigger
> not ok 1 selftests: net/netfilter: conntrack_clash.sh # exit=1
> I think the above should not block the PR, but please have a look.
No idea whats happening, I get 100/100 ok :-/
I'll send a revert or $ksft_skip for now if I can't figure it out.
Powered by blists - more mailing lists