REGTESTS: sample_fetches: pin one thread in the proxy state test

Same reason as for the connection address test: act_conn and fe_conn
are over-counted when several threads accept in parallel on a loaded
machine, which made the connection counters of this test unpredictable
when the suite is run with vtest -j.

diff --git a/reg-tests/sample_fetches/proxy_state.vtc b/reg-tests/sample_fetches/proxy_state.vtc
index 94d6491c31cdd65f4ea4e1b22f608b550f176dbc..9b315647813368d9ebf0013ca1d74ecbec567c5a 100644 (file)
--- a/reg-tests/sample_fetches/proxy_state.vtc
+++ b/reg-tests/sample_fetches/proxy_state.vtc
@@ -6,6 +6,10 @@ varnishtest "Test the proxy and server state sample fetches"
 # usable server and one disabled server so that nbsrv() and srv_is_up()
 # have something to distinguish.
 
+# A single thread is used because act_conn and fe_conn are over-counted
+# when several threads accept in parallel on a loaded machine, which
+# would make the connection counters below unpredictable.
+
 feature ignore_unknown_macro
 
 server s1 {
@@ -17,6 +21,7 @@ haproxy h1 -conf {
     global
     .if feature(THREAD)
         thread-groups 1
+        nbthread 1
     .endif
         chroot /