From 0f98a156a71120e566c715a08683f0a93e9b02d3 Mon Sep 17 00:00:00 2001 From: Christopher Faulet Date: Thu, 2 Jun 2022 13:56:00 +0200 Subject: [PATCH] REGTESTS: abortonclose: Add a barrier to not mix up log messages Depending on the timing, time to time, the log message for "/c4" request can be received before the one for "/c2" request. To (hopefully) fix the issue, a barrier has been added to wait "/c2" log message before sending other requests. --- reg-tests/http-messaging/http_abortonclose.vtc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/reg-tests/http-messaging/http_abortonclose.vtc b/reg-tests/http-messaging/http_abortonclose.vtc index 4dc4bbe880..65831635cb 100644 --- a/reg-tests/http-messaging/http_abortonclose.vtc +++ b/reg-tests/http-messaging/http_abortonclose.vtc @@ -43,7 +43,7 @@ syslog S -level info { barrier b2 sync recv expect ~ "[^:\\[ ]*\\[[0-9]*\\]: .* .* fe1 be1_2/srv1 [0-9]*/[0-9]*/-1/-1/[0-9]* -1 .* - - CC-- .* .* \"GET /c2 HTTP/1\\.1\"" - + barrier b2 sync recv expect ~ "[^:\\[ ]*\\[[0-9]*\\]: .* .* fe2 be2/ [0-9]*/[0-9]*/-1/-1/[0-9]* -1 .* - - CQ-- .* .* \"GET /c4 HTTP/1\\.1\"" barrier b2 sync @@ -114,6 +114,9 @@ client c2 -connect ${h1_fe1_sock} { txreq -url /c2 } -run +# Wait c2 log entry +barrier b2 sync + # server with maxconn=1, abort waiting the server reply : CH-- client c3 -connect ${h1_fe2_sock} { txreq -url /c3