From: Willy Tarreau Date: Sat, 21 Nov 2020 14:33:03 +0000 (+0100) Subject: REGTESTS: mark proxy_protocol_random_fail as broken X-Git-Tag: v2.4-dev1~3 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=41378899111d9bc77c871d0fdc21088cce547054;p=thirdparty%2Fhaproxy.git REGTESTS: mark proxy_protocol_random_fail as broken As indicated in issue #907 it very frequently fails on FreeBSD, and looking at it, it's broken in multiple ways. It relies on log ordering between two layers, the first one being allowed to support h2. Given that on FreeBSD it usually ends up in timeouts, it's very likely that for some reason one frontend logs before the other one or that curl uses h2 instead of h1 there, and that the log instance waits forever for its lines. Usually it works fine when run locally though, so let's not remove it and mark it as broken instead so that it can still be used when relevant. --- diff --git a/reg-tests/connection/proxy_protocol_random_fail.vtc b/reg-tests/connection/proxy_protocol_random_fail.vtc index 7fafc43d3c..983857733f 100644 --- a/reg-tests/connection/proxy_protocol_random_fail.vtc +++ b/reg-tests/connection/proxy_protocol_random_fail.vtc @@ -13,7 +13,7 @@ varnishtest "PROXY protocol random failures" feature ignore_unknown_macro -#REGTEST_TYPE=bug +#REGTEST_TYPE=broken syslog Slog_1 -repeat 8 -level info { recv