From 6773c1144fac05014d2b0236a700d45986ab45bd Mon Sep 17 00:00:00 2001 From: Evan Hunt Date: Thu, 2 Sep 2021 09:11:02 -0700 Subject: [PATCH] increase 1-second timeout in fetchlimit when "checking lame server clients are dropped below the hard limit", periodically a query is sent for a name for which the server is authoritative, to verify that legitimate queries can still be processed while the server is dealing with a flood of lame delegation queries. those queries used the same dig options as elsewhere in the fetchlimit test, including "+tries=1 +timeout=1". on slow systems, a 1-second timeout may be insufficient to get an answer even if the server is behaving well. this commit increases the timeout for the check queries to 2 seconds in hopes that will be enough to eliminate test failures in CI. (cherry picked from commit 45f330339c640dc0c27101942a2a107fa1972dd4) --- bin/tests/system/fetchlimit/tests.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bin/tests/system/fetchlimit/tests.sh b/bin/tests/system/fetchlimit/tests.sh index bf388d2a248..a3ff655bcf3 100644 --- a/bin/tests/system/fetchlimit/tests.sh +++ b/bin/tests/system/fetchlimit/tests.sh @@ -162,7 +162,7 @@ success=0 touch ans4/norespond for try in 1 2 3 4 5; do burst b $try 400 - $DIGCMD a ${try}.example > dig.out.ns3.$try + $DIGCMD +time=2 a ${try}.example > dig.out.ns3.$try stat 400 || exceeded=`expr $exceeded + 1` grep "status: NOERROR" dig.out.ns3.$try > /dev/null 2>&1 && \ success=`expr $success + 1` -- 2.47.3