[Varnish] #1209: Intermittent failure of tests/v00017.vtc
Varnish
varnish-bugs at varnish-cache.org
Wed Oct 10 17:17:45 CEST 2012
#1209: Intermittent failure of tests/v00017.vtc
-------------------+-------------------------
Reporter: mi | Type: defect
Status: new | Priority: low
Milestone: | Component: varnishtest
Version: 3.0.3 | Severity: minor
Keywords: |
-------------------+-------------------------
Although I've run `make check' on this host dozens of times by now --
investigating other test-failures (and fixes), I have not seen this one
fail before. Why is the test only failing ''occasionally''?
{{{
**** top 0.0 macro def varnishd=../varnishd/varnishd
**** top 0.0 macro def
pwd=/mi/ports/www/varnish/work/varnish-3.0.3/bin/varnishtest
**** top 0.0 macro def
topbuild=/mi/ports/www/varnish/work/varnish-3.0.3/bin/varnishtest/../..
**** top 0.0 macro def bad_ip=10.255.255.255
**** top 0.0 macro def tmpdir=/tmp/vtc.95304.0fef08a6
* top 0.0 TEST ./tests/v00017.vtc starting
*** top 0.0 varnishtest
* top 0.0 TEST VCL compiler coverage test: vcc_acl.c
*** top 0.0 varnish
** v1 0.1 Launch
*** v1 0.1 CMD: cd ${pwd} && ${varnishd} -d -d -n
/tmp/vtc.95304.0fef08a6/v1 -l 10m,1m,- -p auto_restart=off -p
syslog_cli_traffic=off -a '127.0.0.1:0' -S /tmp/vtc.95304.0fef08a6/v1/_S
-M '127.0.0.1 56324' -P /tmp/vtc.95304.0fef08a6/v1/varnishd.pid
-sfile,/tmp/vtc.95304.0fef08a6/v1,10M
*** v1 0.1 CMD: cd
/mi/ports/www/varnish/work/varnish-3.0.3/bin/varnishtest &&
../varnishd/varnishd -d -d -n /tmp/vtc.95304.0fef08a6/v1 -l 10m,1m,- -p
auto_restart=off -p syslog_cli_traffic=off -a '127.0.0.1:0' -S
/tmp/vtc.95304.0fef08a6/v1/_S -M '127.0.0.1 56324' -P
/tmp/vtc.95304.0fef08a6/v1/varnishd.pid
-sfile,/tmp/vtc.95304.0fef08a6/v1,10M
*** v1 0.1 PID: 2446
*** v1 0.3 debug| Platform:
FreeBSD,8.3-STABLE,i386,-sfile,-smalloc,-hcritbit\n
*** v1 0.3 debug| 200 236 \n
*** v1 0.3 debug| -----------------------------\n
*** v1 0.3 debug| Varnish Cache CLI 1.0\n
*** v1 0.3 debug| -----------------------------\n
*** v1 0.3 debug| FreeBSD,8.3-STABLE,i386,-sfile,-smalloc,-hcritbit\n
*** v1 0.3 debug| \n
*** v1 0.3 debug| Type 'help' for command list.\n
*** v1 0.3 debug| Type 'quit' to close CLI session.\n
*** v1 0.3 debug| Type 'start' to launch worker process.\n
*** v1 0.3 debug| \n
**** v1 0.4 CLIPOLL 1 0x1 0x0
*** v1 0.4 CLI connection fd = 7
*** v1 0.4 CLI RX 107
**** v1 0.4 CLI RX| ysjyzfatmhgkkcxnbwnmbevdmcunqhgq\n
**** v1 0.4 CLI RX| \n
**** v1 0.4 CLI RX| Authentication required.\n
**** v1 0.5 CLI TX| auth
d996b7a0779290b12e335137cee54c549fa727d306522534e759b3fd87cfc0bb\n
*** v1 0.5 CLI RX 200
**** v1 0.5 CLI RX| -----------------------------\n
**** v1 0.5 CLI RX| Varnish Cache CLI 1.0\n
**** v1 0.5 CLI RX| -----------------------------\n
**** v1 0.5 CLI RX| FreeBSD,8.3-STABLE,i386,-sfile,-smalloc,-hcritbit\n
**** v1 0.5 CLI RX| \n
**** v1 0.5 CLI RX| Type 'help' for command list.\n
**** v1 0.5 CLI RX| Type 'quit' to close CLI session.\n
**** v1 0.5 CLI RX| Type 'start' to launch worker process.\n
**** v1 0.5 CLI TX| vcl.inline vcl1 << %XJEIFLH|)Xspa8P\n
**** v1 0.5 CLI TX| \n
**** v1 0.5 CLI TX| \tbackend b { .host = "127.0.0.1"; }\n
**** v1 0.5 CLI TX| \tacl a { "10.1.2.3"/33; }\n
**** v1 0.5 CLI TX| \tsub vcl_recv { if (client.ip ~ a) { return(pass);
} }\n
**** v1 0.5 CLI TX| \n
**** v1 0.5 CLI TX| %XJEIFLH|)Xspa8P\n
*** v1 0.6 CLI RX 106
**** v1 0.6 CLI RX| Message from VCC-compiler:\n
**** v1 0.6 CLI RX| Too wide mask (33) for IPv4 address('input' Line 3
Pos 28)\n
**** v1 0.6 CLI RX| acl a { "10.1.2.3"/33; }\n
**** v1 0.6 CLI RX| ---------------------------##---\n
**** v1 0.6 CLI RX| \n
**** v1 0.6 CLI RX| Running VCC-compiler failed, exit 1\n
**** v1 0.6 CLI RX| \n
**** v1 0.6 CLI RX| VCL compilation failed
** v1 0.6 VCL compilation failed (as expected)
*** top 0.6 varnish
**** v1 0.6 CLI TX| vcl.inline vcl2 << %XJEIFLH|)Xspa8P\n
**** v1 0.6 CLI TX| \n
**** v1 0.6 CLI TX| \tbackend b { .host = "127.0.0.1"; }\n
**** v1 0.6 CLI TX| \tacl a { "1::2"/129; }\n
**** v1 0.6 CLI TX| \tsub vcl_recv { if (client.ip ~ a) { return(pass);
} }\n
**** v1 0.6 CLI TX| \n
**** v1 0.6 CLI TX| %XJEIFLH|)Xspa8P\n
---- v1 20.6 CLI failed (vcl.inline vcl2 << %XJEIFLH|)Xspa8P
backend b { .host = "127.0.0.1"; }
acl a { "1::2"/129; }
sub vcl_recv { if (client.ip ~ a) { return(pass); } }
%XJEIFLH|)Xspa8P
) = -1 400 CLI communication error (hdr)
---- v1 20.6 VCL compilation got 400 expected 106
* top 20.6 RESETTING after ./tests/v00017.vtc
** v1 21.6 Wait
** v1 21.7 R 2446 Status: 0000
* top 21.7 TEST ./tests/v00017.vtc FAILED
# top TEST ./tests/v00017.vtc FAILED (21.703) exit=1
}}}
Perhaps, the tests should all run under valgrind, when the utility is
available?
--
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1209>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator
More information about the varnish-bugs
mailing list