shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-01 08:58:29 +03:00
Code

test: give sd-resolved enough time to timeout

Browse Source 
The timeout on sd-resolved's side is 5-10s (UDP or TCP), but dig's
default timeout is 5s. Let's give sd-resolved enough time to timeout
before either giving up or checking if it served stale data on dig's
side.

Resolves: #31639
This commit is contained in:
Frantisek Sumsal 2024-04-09 20:15:36 +02:00
parent bfd30e8af6
commit 721e78ff73
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
test/units/testsuite-75.sh
View File

@ -719,7 +719,9 @@ if command -v nft >/dev/null; then
sleep 2
drop_dns_outbound_traffic
set +e
run dig stale1.unsigned.test -t A
# Make sure we give sd-resolved enough time to timeout (5-10s) before giving up
# See: https://github.com/systemd/systemd/issues/31639#issuecomment-2009152617
run dig +tries=1 +timeout=15 stale1.unsigned.test -t A
set -eux
grep -qE "no servers could be reached" "$RUN_OUT"
nft flush ruleset
@ -738,7 +740,8 @@ if command -v nft >/dev/null; then
grep -qE "NOERROR" "$RUN_OUT"
sleep 2
drop_dns_outbound_traffic
run dig stale1.unsigned.test -t A
# Make sure we give sd-resolved enough time to timeout (5-10s) and serve the stale data (see above)
run dig +tries=1 +timeout=15 stale1.unsigned.test -t A
grep -qE "NOERROR" "$RUN_OUT"
grep -qE "10.0.0.112" "$RUN_OUT"