Evan Hunt 5307bf64ce reduce timing dependencies in system tests ... one of the tests in the resolver system test depends on dig getting no response to its first two query attempts, and SERVFAIL on the third after resolution times out. using a 5-second retry timer in dig means the SERVFAIL response could occur while dig is discarding the second query and preparing to send the third. in this case the server's response could be missed. shortening the retry interval to 4 seconds ensures that dig has already sent the third query when the SERVFAIL response arrives. also, the serve-stale system test could fail due to a race in which it timed out after waiting ten seconds for a file to be written, and the dig timeout was just a bit longer. this is addressed by extending the dig timeout to 11 seconds for this test.		2020-11-07 20:49:53 +01:00
..
ans2	update all copyright headers to eliminate the typo	2020-09-14 16:20:40 -07:00
ans3	update all copyright headers to eliminate the typo	2020-09-14 16:20:40 -07:00
ans8	update all copyright headers to eliminate the typo	2020-09-14 16:20:40 -07:00
ns1	further tidying of primary/secondary terminology in system tests	2020-07-01 11:12:12 -07:00
ns4	update all copyright headers to eliminate the typo	2020-09-14 16:20:40 -07:00
ns5	further tidying of primary/secondary terminology in system tests	2020-07-01 11:12:12 -07:00
ns6	update all copyright headers to eliminate the typo	2020-09-14 16:20:40 -07:00
ns7	further tidying of primary/secondary terminology in system tests	2020-07-01 11:12:12 -07:00
clean.sh	update all copyright headers to eliminate the typo	2020-09-14 16:20:40 -07:00
setup.sh	update all copyright headers to eliminate the typo	2020-09-14 16:20:40 -07:00
tests.sh	reduce timing dependencies in system tests	2020-11-07 20:49:53 +01:00