From: Florian Westphal <fw@strlen.de>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] tests: shell: Fix for spurious fail in maps/typeof_maps_add_delete
Date: Fri, 23 Oct 2026 13:56:26 +0200 [thread overview]
Message-ID: <attLaqI7J7QcsupL@strlen.de> (raw)
In-Reply-To: <20261023103603.1048380-1-phil@nwl.cc>
Phil Sutter <phil@nwl.cc> wrote:
> Testing on a (probably slow) aarch64 machine yielded dump failure since
> ruleset listing had '# count 1' appended to map size statement. The 3s
> delay supposedly wasn't long enough for the element to be reapped after
> disabling.
>
> The test itself seems to perform all desired ruleset checks though, so
> just drop the stored dumps to avoid this problem.
Annoying, but spurious failures suck more:
Acked-by: Florian Westphal <fw@strlen.de>
next prev parent reply other threads:[~2026-10-23 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 10:36 [nft PATCH] tests: shell: Fix for spurious fail in maps/typeof_maps_add_delete Phil Sutter
2026-10-23 11:56 ` Florian Westphal [this message]
2026-10-23 13:04 ` Phil Sutter
2026-10-23 13:26 ` Phil Sutter
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=attLaqI7J7QcsupL@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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