Descriptionnet: try to deflake TestVariousDeadlines4Proc
Timeouts are only checked when the non-blocking
network read returns EAGAIN. If the writer is racing
far enough ahead of the reader, it is possible that the
reader may never catch up, and therefore never
reach the timeout check.
This theory is supported by the fact that it is always
the longer timeouts that fail in the build failures.
They give the writer more time to get ahead.
Sleeping in the writer should give the reader time
to catch up.
Patch Set 1 #Patch Set 2 : diff -r ef8878dbed3b https://code.google.com/p/go #Patch Set 3 : diff -r ef8878dbed3b https://code.google.com/p/go #MessagesTotal messages: 3
|