[master] 147dfaf Error messages from Resolve_Sockaddr(UDS) differ on different platforms.

[Geoff Simmons]

commit 147dfafdec75ce6983b09c5c56619fd08a507f72
Author: Geoff Simmons <geoff at uplex.de>
Date:   Thu Feb 22 11:07:24 2018 +0100

    Error messages from Resolve_Sockaddr(UDS) differ on different platforms.
    
    So don't make the test for the error depend on the specific message.
    
    In this case, because getaddrinfo(3) may or may not resolve to a
    sockaddr_un for path if it happens to be a socket (it does on FreeBSD,
    doesn't on Linux).

diff --git a/bin/varnishtest/tests/m00046.vtc b/bin/varnishtest/tests/m00046.vtc
index fc0945b..a5de275 100644
--- a/bin/varnishtest/tests/m00046.vtc
+++ b/bin/varnishtest/tests/m00046.vtc
@@ -21,7 +21,7 @@ client c1 -connect "${tmpdir}/v2.sock" {
 	expect resp.http.v1_addr == "0.0.0.0"
 } -run
 
-varnish v2 -errvcl {IP constant '"${v1_addr}"' could not be resolved to an IP address:} {
+varnish v2 -errvcl {IP constant '"${v1_addr}"'} {
 	import std;
 
 	sub vcl_recv {