[master] 4117949ba coverage: Try to make the tested code actually show up in gcov
Nils Goroll
nils.goroll at uplex.de
Mon Jul 14 16:25:04 UTC 2025
commit 4117949ba257437c2e1cedb5e7a2dbbc2daf88f9
Author: Nils Goroll <nils.goroll at uplex.de>
Date: Mon Jul 14 18:23:57 2025 +0200
coverage: Try to make the tested code actually show up in gcov
I suspect that gcov might not register properly when the process terminates with
a panic?
Ref #4366
diff --git a/bin/varnishtest/tests/m00059.vtc b/bin/varnishtest/tests/m00059.vtc
index 19eb8ce35..07a28b86e 100644
--- a/bin/varnishtest/tests/m00059.vtc
+++ b/bin/varnishtest/tests/m00059.vtc
@@ -1,6 +1,6 @@
varnishtest "VMOD debug.chk*"
-server s1 {
+server s1 -repeat 2 {
rxreq
expect req.url == "/ok"
txresp \
@@ -73,7 +73,13 @@ varnish v1 -vsl_catchup
logexpect l1 -wait
logexpect l2 -wait
-client c1 {
+varnish v1 -stop
+
+varnish v1 -start
+
+client c2 {
+ txreq -url "/ok"
+ rxresp
txreq -url "/wrong" -hdr "panic: yes"
rxresp
} -run
More information about the varnish-commit
mailing list