From e3aa6133952b898c07098c918585778ee4b4365e Mon Sep 17 00:00:00 2001
From: Nils Goroll <nils.goroll@uplex.de>
Date: Fri, 13 Dec 2024 11:50:46 +0100
Subject: [PATCH] vtc: try to stabilize b84

from vtest:

**   top   === process p1 -stop -wait
**** dT    1.431
**** p1    Sent signal 15
**** p1    stdout read 0
**** p1    stderr read 0
**   p1    WAIT4 pid=26430 status=0x000f (user 0.004683 sys 0.009366)
...
**** top   shell_cmd|\ttest ! -f "/root/VT/_vtest_tmp/vtc.26358.31f097e1"/v2/_.secret
**** dT    2.455
**** top   shell_status = 0x0001
---- top   shell_exit not as expected: got 0x0001 wanted 0x0000

Not exactly sure why we see a status != 0 here, but maybe the kill is too early?
---
 bin/varnishtest/tests/b00084.vtc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/bin/varnishtest/tests/b00084.vtc b/bin/varnishtest/tests/b00084.vtc
index 6797d28e61f..d3d5e17f906 100644
--- a/bin/varnishtest/tests/b00084.vtc
+++ b/bin/varnishtest/tests/b00084.vtc
@@ -35,6 +35,8 @@ shell -match _.secret {
 	find "${tmpdir}"/v2/_.secret -perm 0640 -size 256c
 }
 
+shell "varnishadm -n ${tmpdir}/v2 ping"
+
 process p1 -stop -wait
 
 shell {