Willy Tarreau 036ab62231 REGTESTS: fix random failures with wrong_ip_port_logging.vtc under load ... This test has an expect rule for syslog that looks for [cC]D, to indicate a client abort or timeout during the data phase. The purpose was to say that when it fails it must be this, but the very low timeout (1ms) still makes it prone to succeeding if the machine is highly loaded. This has become more visible since commit e8b1ad4c2b ("BUG/MEDIUM: clock: also update the date offset on time jumps") because the clock drift adjustments are more systematic. Since this commit, running 50 such tests at twice more than the number of CPUs in parallel is sufficient to yield errors due to some lines appearing as succeeding: make reg-tests -- --j $((($(nproc)+1)*2)) --vtestparams -n50 reg-tests/log/wrong_ip_port_logging.vtc It was observed that pauses up to 300ms were observed in epoll_wait() in such circumstances, which were properly fixed by the time drift detection.. Another approach would consist in increasing the permitted margin during which we don't fix the clock drift but that would not be logical since the base time had really been awaited for. This should be backported to all stable releases since the commit above will trigger the issue more often.		2024-09-09 19:38:28 +02:00
..
last_rule.vtc	REGTESTS: log: Reduce again response inspect-delay for last_rule.vtc	2023-05-17 11:12:25 +02:00
load_balancing.vtc	REGTESTS: Remove REQUIRE_VERSION=2.0 from all tests	2023-01-05 09:11:38 +01:00
log_backend.vtc	MINOR: log/balance: rename "log-sticky" to "sticky"	2023-11-23 18:21:31 +01:00
log_forward.vtc	…
log_profiles.vtc	MINOR: log: "drop" support for log-profile steps	2024-08-19 18:53:01 +02:00
log_uri.vtc	REGTESTS: fix the race conditions in log_uri.vtc	2023-04-14 12:13:09 +02:00
wrong_ip_port_logging.vtc	REGTESTS: fix random failures with wrong_ip_port_logging.vtc under load	2024-09-09 19:38:28 +02:00