3 Commits

Author	SHA1	Message	Date
Willy Tarreau	f673923629	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 17:57:11 +01:00
Christopher Faulet	85a813676f	REGTESTS: Fix required versions for several scripts ... The following scripts require HAProxy 2.4 : * cache/caching_rules.vtc * cache/post_on_entry.vtc * cache/vary.vtc * checks/1be_40srv_odd_health_checks.vtc * checks/40be_2srv_odd_health_checks.vtc * checks/4be_1srv_health_checks.vtc * converter/fix.vtc * converter/mqtt.vtc * http-messaging/protocol_upgrade.vtc * http-messaging/websocket.vtc * http-set-timeout/set_timeout.vtc * log/log_uri.vtc However it may change is features are backported.	2021-01-28 16:37:14 +01:00
Amaury Denoyelle	78ea5c99a9	REGTESTS: add regtest for http-request set-timeout ... This test compares the timeout value for requests using the sample fetches in accordance with the application of set-timeout rules.	2020-12-11 12:01:07 +01:00