[master] 490a552 We cannot expect there to be a full second between the Bereq/Beresp timestamps, when the Bereq timestamp is taken after our write(2) to the socket, which may have caused us to loose the CPU.

[Poul-Henning Kamp]

commit 490a55223c7d574df38622ea62d77b072293733d
Author: Poul-Henning Kamp <phk at FreeBSD.org>
Date:   Mon May 18 20:36:29 2015 +0000

    We cannot expect there to be a full second between the Bereq/Beresp
    timestamps, when the Bereq timestamp is taken after our write(2)
    to the socket, which may have caused us to loose the CPU.

diff --git a/bin/varnishtest/tests/s00004.vtc b/bin/varnishtest/tests/s00004.vtc
index 169d6ab..cfdc766 100644
--- a/bin/varnishtest/tests/s00004.vtc
+++ b/bin/varnishtest/tests/s00004.vtc
@@ -36,7 +36,7 @@ logexpect l1 -v v1 -g request {
 	expect 0 1002	Begin		bereq
 	expect * =	Timestamp	{Start: \S+ 0\.000000 0\.000000}
 	expect * =	Timestamp	{Bereq: \S+ 0\.\d+ 0\.\d+}
-	expect * =	Timestamp	{Beresp: \S+ 1\.\d+ 1\.\d+}
+	expect * =	Timestamp	{Beresp: \S+ 1\.\d+ [01]\.\d+}
 	expect * =	Timestamp	{BerespBody: \S+ 2\.\d+ 1\.\d+}
 	expect * =	End
 	expect 0 1003	Begin		req 1001 restart