If something causes the recorded tests to deviate from the expected
flows, they might wait forever for data that is not coming. Add a short
timeout, after which a useful error message is shown.
Change-Id: Ib11ccc0e17dcb8b2180493556017275678abbb08
Reviewed-on: https://go-review.googlesource.com/c/144116
Run-TryBot: Filippo Valsorda <filippo@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Adam Langley <agl@golang.org>
}
for i, b := range flows {
if i%2 == 1 {
+ serverConn.SetWriteDeadline(time.Now().Add(1 * time.Second))
serverConn.Write(b)
continue
}
bb := make([]byte, len(b))
+ serverConn.SetReadDeadline(time.Now().Add(1 * time.Second))
_, err := io.ReadFull(serverConn, bb)
if err != nil {
t.Fatalf("%s #%d: %s", test.name, i, err)
}
for i, b := range flows {
if i%2 == 0 {
+ clientConn.SetWriteDeadline(time.Now().Add(1 * time.Second))
clientConn.Write(b)
continue
}
bb := make([]byte, len(b))
+ clientConn.SetReadDeadline(time.Now().Add(1 * time.Second))
n, err := io.ReadFull(clientConn, bb)
if err != nil {
t.Fatalf("%s #%d: %s\nRead %d, wanted %d, got %x, wanted %x\n", test.name, i+1, err, n, len(bb), bb[:n], b)