From e8300966510001e38f2b6530607bac2a93de5c2e Mon Sep 17 00:00:00 2001 From: Phil Sutter Date: Mon, 2 Aug 2021 14:35:08 +0200 Subject: [PATCH] tests: shell: Fix bogus testsuite failure with 100Hz Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1919203 Upstream Status: nftables commit c9c5b5f621c37 commit c9c5b5f621c37d17140dac682d211825ef321093 Author: Phil Sutter Date: Mon Jul 26 15:27:32 2021 +0200 tests: shell: Fix bogus testsuite failure with 100Hz On kernels with CONFIG_HZ=100, clock granularity does not allow tracking timeouts in single digit ms range. Change sets/0031set_timeout_size_0 to not expose this detail. Signed-off-by: Phil Sutter Acked-by: Florian Westphal --- tests/shell/testcases/sets/0031set_timeout_size_0 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/shell/testcases/sets/0031set_timeout_size_0 b/tests/shell/testcases/sets/0031set_timeout_size_0 index 9edd5f6..796640d 100755 --- a/tests/shell/testcases/sets/0031set_timeout_size_0 +++ b/tests/shell/testcases/sets/0031set_timeout_size_0 @@ -3,10 +3,10 @@ RULESET="add table x add set x y { type ipv4_addr; size 128; timeout 30s; flags dynamic; } add chain x test -add rule x test set update ip saddr timeout 1d2h3m4s8ms @y +add rule x test set update ip saddr timeout 1d2h3m4s10ms @y add rule x test set update ip daddr timeout 100ms @y" set -e $NFT -f - <<< "$RULESET" -$NFT list chain x test | grep -q 'update @y { ip saddr timeout 1d2h3m4s8ms }' +$NFT list chain x test | grep -q 'update @y { ip saddr timeout 1d2h3m4s10ms }' $NFT list chain x test | grep -q 'update @y { ip daddr timeout 100ms }' -- 2.31.1