From a1af38b74e99975d326baf52eb995629598c7213 Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Wed, 19 Aug 2020 11:20:28 +0200 Subject: [PATCH] REGTEST: remove stray leading spaces in converteers_ref_cnt_never_dec.vtc Since commit f92afb732 ("MEDIUM: cfgparse: Emit hard error on truncated lines") we now produce parsing errors on truncated lines, in an effort to clean up dangerous or broken config files. And it turns out that one of our own regression tests was suffering from this, as diagnosed by William and Tim. The cause is the leading spaces in front of "} -start" that vtest makes part of the output file, so the file finishes with a partial line made of spaces. --- reg-tests/stick-table/converteers_ref_cnt_never_dec.vtc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reg-tests/stick-table/converteers_ref_cnt_never_dec.vtc b/reg-tests/stick-table/converteers_ref_cnt_never_dec.vtc index d4fb8620d..9af7a544f 100644 --- a/reg-tests/stick-table/converteers_ref_cnt_never_dec.vtc +++ b/reg-tests/stick-table/converteers_ref_cnt_never_dec.vtc @@ -59,7 +59,7 @@ haproxy h1 -conf { http-request redirect location https://${s1_addr}:${s1_port}/ if { req.hdr(X-Forwarded-For),table_sess_cnt(http1) -m int lt 0 } http-request redirect location https://${s1_addr}:${s1_port}/ if { req.hdr(X-Forwarded-For),table_sess_rate(http1) -m int lt 0 } http-request redirect location https://${s1_addr}:${s1_port}/ if { req.hdr(X-Forwarded-For),table_trackers(http1) -m int lt 0 } - } -start +} -start client c1 -connect ${h1_my_frontend_fd_sock} { txreq -url "/" -hdr "X-Forwarded-For: 127.0.0.1"