Ondřej Surý d3b975abb6 Increase the timeout to 15 seconds for the resolver test ... 1. 10 seconds is an unfortunate pick because that reintroduces the problem described in commit 5307bf64 (for an earlier check). Change the +tries=3 +timeout=10 to +tries=2 +time=15, so that we minimize the risk of dig missing any responses sent by the server in the first 15 seconds while also increasing our chances of the response arriving in time on machines under heavy load and allowing it a single retry in case things go awry. 2. The comment about TCP above was misleading: as painfully proven by GitLab CI, using TCP is no guarantee of receiving a response in a timely manner. It may help a bit, but it is certainly not a 100% reliable solution. Change the dig invocation to just use UDP like in the two prior tests for consistency (and revise that comment accordingly).		2022-01-14 13:00:56 +01:00
..
ans2	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
ans3	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
ans8	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
ns1	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
ns4	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
ns5	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
ns6	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
ns7	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
clean.sh	Make resolver system test shellcheck clean	2022-01-14 11:13:26 +01:00
setup.sh	Make resolver system test shellcheck clean	2022-01-14 11:13:26 +01:00
tests.sh	Increase the timeout to 15 seconds for the resolver test	2022-01-14 13:00:56 +01:00