Linux Netfilter development
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: 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 15:26:38 +0200	[thread overview]
Message-ID: <attgjloxT80PCoq0@orbyte.nwl.cc> (raw)
In-Reply-To: <20261023103603.1048380-1-phil@nwl.cc>

On Fri, Oct 23, 2026 at 12:36:03PM +0200, Phil Sutter 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.
> 
> Fixes: a8260c056a69a ("tests: add dynmap datapath add/delete test case")
> Signed-off-by: Phil Sutter <phil@nwl.cc>

Patch applied.

      parent reply	other threads:[~2026-10-23 13:26 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
2026-10-23 13:04   ` Phil Sutter
2026-10-23 13:26 ` Phil Sutter [this message]

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=attgjloxT80PCoq0@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --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