RepoMirrors
/
haproxy
mirror of http://git.haproxy.org/git/haproxy.git/
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
haproxy/reg-tests/seamless-reload/abns_socket.vtc

56 lines
1.8 KiB
Plaintext
Raw Normal View History

MINOR: reg-tests: Add a few regression testing files.
2018-06-20 05:26:44 +00:00
# commit b4dd15b
# BUG/MINOR: unix: Make sure we can transfer abns sockets on seamless reload.
#
# When checking if a socket we got from the parent is suitable for a listener,
# we just checked that the path matched sockname.tmp, however this is
# unsuitable for abns sockets, where we don't have to create a temporary
# file and rename it later.
# To detect that, check that the first character of the sun_path is 0 for
# both, and if so, that &sun_path[1] is the same too.
REGTESTS: mark abns_socket as working now William noticed that the real issue in the abns test was that it was failing to rebind some listeners, issues which were addressed in the previous commits (in some cases, the master would even accept traffic on the worker's socket which was not properly disabled, causing some of the strange error messages). The other issue documented in commit 2ea15a080 was the lack of reliability when the test was run in parallel. This is caused by the abns socket which uses a hard-coded address, making all tests in parallel to step onto each others' toes. Since vtest cannot provide abns sockets, we're instead concatenating the number of the listening port that vtest allocated for another frontend to the abns path, which guarantees to make them unique in the system. The test works fine in all cases now, even with 100 in parallel.
2020-11-03 17:43:48 +00:00
#
# Note: there are some tricks here. One of them is that we must not bind the
# same abns address to multiple processes that may run in parallel. Since
# vtest cannot provide abns sockets, we're instead concatenating the number
# of the listening port that vtest allocated for another frontend to the abns
# path, which guarantees to make them unique in the system.
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 05:26:44 +00:00
varnishtest "Seamless reload issue with abns sockets"
feature ignore_unknown_macro
REGTESTS: try to activate again the seamless reload test with the master CLI Since the reload is now synchronous over the master CLI, try to reload with it. This was a problem before with the signals because it wasn't possible to wait for the end of the reload before sending the requests. This activate again this test, we will see if it's more stable or we will deactivate it again..
2023-11-17 16:11:42 +00:00
feature cmd "command -v socat"
feature cmd "command -v grep"
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 05:26:44 +00:00
REGTEST/MINOR: skip seamless-reload test with abns socket on freebsd abns sockets are not available on freebsd as such mark the test to skip this OS and expose-fd was implemented first in 1.8 so require that
2018-12-08 19:51:16 +00:00
# abns@ sockets are not available on freebsd
REGTEST: exclude OSX and generic targets from abns_socket.vtc This one relies on Linux's abstract namespace sockets which are not available there. FreeBSD used to already be excluded.
2019-04-25 06:50:25 +00:00
#EXCLUDE_TARGETS=freebsd,osx,generic
REGTESTS: try to activate again the seamless reload test with the master CLI Since the reload is now synchronous over the master CLI, try to reload with it. This was a problem before with the signals because it wasn't possible to wait for the end of the reload before sending the requests. This activate again this test, we will see if it's more stable or we will deactivate it again..
2023-11-17 16:11:42 +00:00
#REGTEST_TYPE=devel
REGTEST/MINOR: skip seamless-reload test with abns socket on freebsd abns sockets are not available on freebsd as such mark the test to skip this OS and expose-fd was implemented first in 1.8 so require that
2018-12-08 19:51:16 +00:00
REGTESTS: try to activate again the seamless reload test with the master CLI Since the reload is now synchronous over the master CLI, try to reload with it. This was a problem before with the signals because it wasn't possible to wait for the end of the reload before sending the requests. This activate again this test, we will see if it's more stable or we will deactivate it again..
2023-11-17 16:11:42 +00:00
haproxy h1 -W -S -conf {
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 05:26:44 +00:00
global
REGTEST: Missing enclosing quotes for ${tmpdir} macro.
2018-12-20 08:55:44 +00:00
stats socket "${tmpdir}/h1/stats" level admin expose-fd listeners
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 05:26:44 +00:00
defaults
mode http
log global
option httplog
REGTESTS: extend the default I/O timeouts and make them overridable With the CI occasionally slowing down, we're starting to see again some spurious failures despite the long 1-second timeouts. This reports false positives that are disturbing and doesn't provide as much value as this could. However at this delay it already becomes a pain for developers to wait for the tests to complete. This commit adds support for the new environment variable HAPROXY_TEST_TIMEOUT that will allow anyone to modify the connect, client and server timeouts. It was set to 5 seconds by default, which should be plenty for quite some time in the CI. All relevant values that were 200ms or above were replaced by this one. A few larger values were left as they are special. One test for the set-timeout action that used to rely on a fixed 1-sec value was extended to a fixed 5-sec, as the timeout is normally not reached, but it needs to be known to compare the old and new values.
2021-11-18 16:46:22 +00:00
timeout connect "${HAPROXY_TEST_TIMEOUT-5s}"
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 05:26:44 +00:00
listen testme
bind "fd@${testme}"
REGTESTS: mark abns_socket as working now William noticed that the real issue in the abns test was that it was failing to rebind some listeners, issues which were addressed in the previous commits (in some cases, the master would even accept traffic on the worker's socket which was not properly disabled, causing some of the strange error messages). The other issue documented in commit 2ea15a080 was the lack of reliability when the test was run in parallel. This is caused by the abns socket which uses a hard-coded address, making all tests in parallel to step onto each others' toes. Since vtest cannot provide abns sockets, we're instead concatenating the number of the listening port that vtest allocated for another frontend to the abns path, which guarantees to make them unique in the system. The test works fine in all cases now, even with 100 in parallel.
2020-11-03 17:43:48 +00:00
server test_abns_server abns@wpproc1_${h1_testme_port} send-proxy-v2
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 05:26:44 +00:00
frontend test_abns
REGTESTS: mark abns_socket as working now William noticed that the real issue in the abns test was that it was failing to rebind some listeners, issues which were addressed in the previous commits (in some cases, the master would even accept traffic on the worker's socket which was not properly disabled, causing some of the strange error messages). The other issue documented in commit 2ea15a080 was the lack of reliability when the test was run in parallel. This is caused by the abns socket which uses a hard-coded address, making all tests in parallel to step onto each others' toes. Since vtest cannot provide abns sockets, we're instead concatenating the number of the listening port that vtest allocated for another frontend to the abns path, which guarantees to make them unique in the system. The test works fine in all cases now, even with 100 in parallel.
2020-11-03 17:43:48 +00:00
bind abns@wpproc1_${h1_testme_port} accept-proxy
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 05:26:44 +00:00
http-request deny deny_status 200
} -start
shell {
REGTESTS: try to activate again the seamless reload test with the master CLI Since the reload is now synchronous over the master CLI, try to reload with it. This was a problem before with the signals because it wasn't possible to wait for the end of the reload before sending the requests. This activate again this test, we will see if it's more stable or we will deactivate it again..
2023-11-17 16:11:42 +00:00
echo "reload" | socat -t1000 TCP:${h1_mcli_addr}:${h1_mcli_port} - | grep 'Success=1'
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 05:26:44 +00:00
}
client c1 -connect ${h1_testme_sock} {
txreq -url "/"
rxresp
} -repeat 50 -run