upstream/haproxy
1
0
Fork 0
mirror of https://github.com/haproxy/haproxy.git synced 2026-06-08 16:23:24 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
haproxy/reg-tests/converter/json.vtc

46 lines
910 B
Text
Raw Permalink Normal View History

CLEANUP: sample: remove uneeded check in json validation - check functions are never called with a NULL args list, it is always an array, so first check can be removed - the expression parser guarantees that we can't have anything else, because we mentioned json converter takes a mandatory string argument. Thus test on `ARGT_STR` can be removed as well - also add breaking line between enum and function declaration In order to validate it, add a simple json test testing very simple cases but can be improved in the future: - default json converter without args - json converter failing on error (utf8) - json converter with error being removed (utf8s) Signed-off-by: William Dauchy <wdauchy@gmail.com>
2021-01-08 15:57:41 -05:00
varnishtest "json converter test"
feature ignore_unknown_macro
server s1 {
rxreq
txresp
} -repeat 2 -start
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 {
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
CLEANUP: sample: remove uneeded check in json validation - check functions are never called with a NULL args list, it is always an array, so first check can be removed - the expression parser guarantees that we can't have anything else, because we mentioned json converter takes a mandatory string argument. Thus test on `ARGT_STR` can be removed as well - also add breaking line between enum and function declaration In order to validate it, add a simple json test testing very simple cases but can be improved in the future: - default json converter without args - json converter failing on error (utf8) - json converter with error being removed (utf8s) Signed-off-by: William Dauchy <wdauchy@gmail.com>
2021-01-08 15:57:41 -05:00
defaults
mode http
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}"
CLEANUP: sample: remove uneeded check in json validation - check functions are never called with a NULL args list, it is always an array, so first check can be removed - the expression parser guarantees that we can't have anything else, because we mentioned json converter takes a mandatory string argument. Thus test on `ARGT_STR` can be removed as well - also add breaking line between enum and function declaration In order to validate it, add a simple json test testing very simple cases but can be improved in the future: - default json converter without args - json converter failing on error (utf8) - json converter with error being removed (utf8s) Signed-off-by: William Dauchy <wdauchy@gmail.com>
2021-01-08 15:57:41 -05:00
frontend fe
bind "fd@${fe}"
http-response set-header json0 "%[str(foo 1/2),json]"
# bad UTF-8 sequence
http-response set-header json1 "%[str(\xE0),json(utf8)]"
# bad UTF-8 sequence, but removes them
http-response set-header json2 "%[str(-\xE0-),json(utf8s)]"
default_backend be
backend be
server s1 ${s1_addr}:${s1_port}
} -start
client c1 -connect ${h1_fe_sock} {
txreq -url "/"
rxresp
expect resp.http.json0 == "foo 1\\/2"
expect resp.http.json1 == ""
expect resp.http.json2 == "--"
expect resp.status == 200
} -run
Reference in a new issue Copy permalink