ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

improve dyndb test resilience

Browse Source 
- no longer grep for specific line numbers when checking
  parameter logging, as those can change
- report the failure immediatey if parameter check fails
This commit is contained in:
Evan Hunt
2018-02-23 10:08:51 -08:00
parent 9425d6ba7c
commit 749df056be
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
bin/tests/system/dyndb/tests.sh
View File

@@ -129,8 +129,9 @@ test_del test4.ipv6.example.nil. AAAA || ret=1
status=`expr $status + $ret`
newtest "checking parameter logging"
grep "loading params for dyndb 'sample' from .*named.conf:36" ns1/named.run > /dev/null || ret=1
grep "loading params for dyndb 'sample2' from .*named.conf:37" ns1/named.run > /dev/null || ret=1
grep "loading params for dyndb 'sample' from .*named.conf:" ns1/named.run > /dev/null || ret=1
grep "loading params for dyndb 'sample2' from .*named.conf:" ns1/named.run > /dev/null || ret=1
[ $ret -eq 1 ] && echo_i "failed"
status=`expr $status + $ret`
echo_i "checking dyndb still works after reload"