From: Witold Kręcicki Date: Wed, 28 Nov 2018 13:59:38 +0000 (+0000) Subject: Fetchlimit test: update softquota limit to 380. X-Git-Tag: v9.13.5~16^2~1 X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=a48ca15e77f47dfc10f7b0673eeb936d1a8ba7ef;p=thirdparty%2Fbind9.git Fetchlimit test: update softquota limit to 380. In the test the quota is set to 400, and softquota to 90%*400=360. We first attach to quota, and then if we're above softquota we drop the oldest client. With new socket code and taskmgr it's parallel enough to create a race between multiple instances doing 'attach to quota' and then 'drop oldest client' - making number of clients go over softquota. It's not a problem in real life, as it's just soft quota. --- diff --git a/bin/tests/system/fetchlimit/tests.sh b/bin/tests/system/fetchlimit/tests.sh index 55309d7b3c3..d7fb00a4935 100644 --- a/bin/tests/system/fetchlimit/tests.sh +++ b/bin/tests/system/fetchlimit/tests.sh @@ -166,7 +166,7 @@ touch ans4/norespond for try in 1 2 3 4 5; do burst b $try 400 $DIG @10.53.0.3 -p ${PORT} a ${try}.example > dig.out.ns3.$try - stat 370 || exceeded=`expr $exceeded + 1` + stat 380 || exceeded=`expr $exceeded + 1` grep "status: NOERROR" dig.out.ns3.$try > /dev/null 2>&1 && \ success=`expr $success + 1` grep "status: SERVFAIL" dig.out.ns3.$try > /dev/null 2>&1 && \ @@ -177,7 +177,7 @@ echo_i "$success successful valid queries (expected 5)" [ "$success" -eq 5 ] || { echo_i "failed"; ret=1; } echo_i "$fail SERVFAIL responses (expected 0)" [ "$fail" -eq 0 ] || { echo_i "failed"; ret=1; } -echo_i "clients count exceeded 370 on $exceeded trials (expected 0)" +echo_i "clients count exceeded 380 on $exceeded trials (expected 0)" [ "$exceeded" -eq 0 ] || { echo_i "failed"; ret=1; } if [ $ret != 0 ]; then echo_i "failed"; fi status=`expr $status + $ret`