upstream/haproxy
1
0
Fork 0
mirror of https://github.com/haproxy/haproxy.git synced 2026-04-23 15:19:36 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
haproxy/reg-tests/spoe/wrong_init.vtc

28 lines
710 B
Text
Raw Normal View History

MINOR: reg-tests: Add a few regression testing files.
2018-06-20 01:26:44 -04:00
# commit 84c844eb12b250aa86f2aadaff77c42dfc3cb619
# BUG/MINOR: spoe: Initialize variables used during conf parsing before any check
#
# Some initializations must be done at the beginning of parse_spoe_flt to avoid
CLEANUP: assorted typo fixes in the code and comments These are mostly comments in the code. A few error messages were fixed and are of low enough importance not to deserve a backport. Some regtests were also fixed.
2020-03-10 03:06:11 -04:00
# segmentation fault when first errors are caught, when the "filter spoe" line is
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 01:26:44 -04:00
# parsed.
REGTEST: replace LEVEL option by a more human readable one. This patch replaces LEVEL variable by REGTESTS_TYPES variable which is more mnemonic and human readable. It is uses as a filter to run the reg tests scripts where a commented #REGTEST_TYPE may be defined to designate their types. Running the following command: $ REGTESTS_TYPES=slow,default will start all the reg tests where REGTEST_TYPE is defines as 'slow' or 'default'. Note that 'default' is also the default value of REGTEST_TYPE when not specified dedicated to run all the current h*.vtc files. When REGTESTS_TYPES is not specified there is no filter at all. All the tests are run. This patches also defines REGTEST_TYPE with 'slow' value for all the s*.vtc files, 'bug' value for al the b*.vtc files, 'broken' value for all the k*.vtc files.
2019-03-29 10:07:24 -04:00
#REGTEST_TYPE=bug
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 01:26:44 -04:00
varnishtest "SPOE bug: missing configuration file"
REGTEST/MINOR: Missing mandatory "ignore_unknown_macro". Since bbc34e2 varnish commit (for varnishtest), a new "cli" macro is automatically created for each VTC script to dialog with the CLI. Consequently, as this macro is unknown from higher level code for varnishtest, it makes the scripts fail if we we do not ask varnishtest to disregard the unknown macros. To prevent this, from now on, for each VTC file for haproxy we MUST add "feature ignore_unknown_macro" line to do so. This is mandatory
2018-08-21 09:29:24 -04:00
feature ignore_unknown_macro
REGTESTS: use -dW by default on every reg-tests Every reg-test now runs without any warning, so let's acivate -dW by default so the new ones will inheritate the option. This patch reverts 9d511b3c ("REGTESTS: enable -dW on almost all tests to fail on warnings") and adds -dW in the default HAPROXY_ARGS of scripts/run-regtests.sh instead.
2024-11-19 10:51:30 -05:00
haproxy h1 -conf-BAD {} {
REGTESTS: restrict execution to a single thread group When threads are enabled and running on a machine with multiple CCX or multiple nodes, thread groups are now enabled since 3.3-dev2, causing load-balancing algorithms to randomly fail due to incoming connections spreading over multiple groups and using different load balancing indexes. Let's just force "thread-groups 1" into all configs when threads are enabled to avoid this.
2025-06-30 12:44:07 -04:00
global
.if feature(THREAD)
thread-groups 1
.endif
MINOR: reg-tests: Add a few regression testing files.
2018-06-20 01:26:44 -04:00
defaults
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 11:46:22 -05: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 01:26:44 -04:00
frontend my-front
filter spoe
}
Reference in a new issue Copy permalink