upstream/haproxy
1
0
Fork 0
mirror of https://github.com/haproxy/haproxy.git synced 2026-06-10 17:32:03 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 10

REGTESTS: Don't try to use real nameservers for testcases
Some checks are pending
Contrib / admin/halog/ (push) Waiting to run
Details
Contrib / dev/flags/ (push) Waiting to run
Details
Contrib / dev/haring/ (push) Waiting to run
Details
Contrib / dev/hpack/ (push) Waiting to run
Details
Contrib / dev/poll/ (push) Waiting to run
Details
VTest / Generate Build Matrix (push) Waiting to run
Details
VTest / (push) Blocked by required conditions
Details
Windows / Windows, gcc, all features (push) Waiting to run
Details

Browse source 
The test doesn't need a real nameserver and in a isolated, restricted
test environment it might not be able to reach one at all, like with a
network sandbox. So lets just use 127.0.0.1:53. Even if there is none,
that's not a problem for this particular test.

Signed-off-by: Christian Ruppert <idl0r@qasl.de>
This commit is contained in:
Christian Ruppert 2026-05-11 19:48:23 +02:00 committed by Willy Tarreau
parent 80fd275773
commit ae614e24c3
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
reg-tests/server/cli_set_fqdn.vtc
View file

@ -42,7 +42,7 @@ haproxy h2 -conf {
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
resolvers systemdns
parse-resolv-conf
nameserver dns1 127.0.0.1:53
frontend myfrontend
bind "fd@${my_fe}"