summaryrefslogtreecommitdiffstats
path: root/tests/shell/testcases/rule_management/dumps/0011reset_0.nft
diff options
context:
space:
mode:
authorFlorian Westphal <fw@strlen.de>2025-04-08 16:21:32 +0200
committerFlorian Westphal <fw@strlen.de>2025-06-22 21:40:40 +0200
commit7b21b7e387e30de4c4147c82247655cca608d2fd (patch)
tree37d4390cfe185733c8215f6e905248ced9508678 /tests/shell/testcases/rule_management/dumps/0011reset_0.nft
parent8ff87c8fd483eb3fdab5839cccaf100b593fe92e (diff)
tests: shell: add feature check for count output change
New kernels with latest nft release will print the number of set elements allocated on the kernel side. This causes shell test dump validation to fail in several places. We can't just update the affected dump files because the test cases are also supposed to pass on current -stable releases. Add a feature check for this. Dump failure can then use sed to postprocess the stored dump file and can then call diff a second time. Signed-off-by: Florian Westphal <fw@strlen.de>
Diffstat (limited to 'tests/shell/testcases/rule_management/dumps/0011reset_0.nft')
-rw-r--r--tests/shell/testcases/rule_management/dumps/0011reset_0.nft2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/shell/testcases/rule_management/dumps/0011reset_0.nft b/tests/shell/testcases/rule_management/dumps/0011reset_0.nft
index 3b4f5a11..3c29b582 100644
--- a/tests/shell/testcases/rule_management/dumps/0011reset_0.nft
+++ b/tests/shell/testcases/rule_management/dumps/0011reset_0.nft
@@ -1,7 +1,7 @@
table ip t {
set s {
type ipv4_addr
- size 65535
+ size 65535 # count 1
flags dynamic
counter
elements = { 1.1.1.1 counter packets 1 bytes 11 }