Commit 490a5522 authored by Poul-Henning Kamp's avatar Poul-Henning Kamp

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.
parent ba2d2e00
......@@ -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
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment