Revert the statistics system test change after we fixed the resolver
When the resolver was refactored, the statistics system test had to be
adjusted in c6b4d82557. Unfortunately,
this change had to be done because of an error in the resolver
refactoring where timeout would not retry next server, but keep trying
the same server. As we have now fixed this bug, revert the change to
the test back to the previous state.
This commit is contained in:
@@ -139,13 +139,11 @@ n=`expr $n + 1`
|
||||
|
||||
ret=0
|
||||
echo_i "checking priming queries are counted ($n)"
|
||||
grep "1 priming queries" $last_stats > /dev/null || ret=1
|
||||
grep "priming queries" $last_stats > /dev/null || ret=1
|
||||
if [ $ret != 0 ]; then echo_i "failed"; fi
|
||||
status=`expr $status + $ret`
|
||||
n=`expr $n + 1`
|
||||
|
||||
wait_for_log 10 "connection refused" ns3/named.stats
|
||||
|
||||
ret=0
|
||||
echo_i "checking that zones with slash are properly shown in XML output ($n)"
|
||||
if $FEATURETEST --have-libxml2 && [ -x ${CURL} ] ; then
|
||||
@@ -234,7 +232,7 @@ if $FEATURETEST --have-libxml2 && [ -e stats.xml.out ] && [ -x "${XSLTPROC}" ]
|
||||
# Socket statistics (expect no errors)
|
||||
grep "<counter name=\"TCP4AcceptFail\">0</counter>" stats.xml.out >/dev/null || ret=1
|
||||
grep "<counter name=\"TCP4BindFail\">0</counter>" stats.xml.out >/dev/null || ret=1
|
||||
grep "<counter name=\"TCP4ConnFail\">1</counter>" stats.xml.out >/dev/null || ret=1
|
||||
grep "<counter name=\"TCP4ConnFail\">0</counter>" stats.xml.out >/dev/null || ret=1
|
||||
grep "<counter name=\"TCP4OpenFail\">0</counter>" stats.xml.out >/dev/null || ret=1
|
||||
grep "<counter name=\"TCP4RecvErr\">0</counter>" stats.xml.out >/dev/null || ret=1
|
||||
# grep "<counter name=\"TCP4SendErr\">0</counter>" stats.xml.out >/dev/null || ret=1
|
||||
|
||||
Reference in New Issue
Block a user