mirror of
https://github.com/golang/go
synced 2024-11-02 15:37:45 +00:00
net: lengthen arbitrary SetDeadline timeout by a few orders of magnitude
The "someTimeout" constant in the net test is “just to test that net.Conn implementations don't explode when their SetFooDeadline methods are called”. It was set to 10 seconds, which is short enough that it could actually matter on some platforms. Since the point of the constant is just to make sure methods don't explode, we should set it to be at least a couple of orders of magnitude longer than the test: then it is guaranteed not to have any unintended side-effects. Fixes #50227 Change-Id: If97ae7bef5e7f16b336d09ccc37f5ea2ea7e70b3 Reviewed-on: https://go-review.googlesource.com/c/go/+/372796 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
This commit is contained in:
parent
63077bfcf5
commit
55a25aa6ca
1 changed files with 1 additions and 1 deletions
|
@ -17,7 +17,7 @@ import (
|
|||
// someTimeout is used just to test that net.Conn implementations
|
||||
// don't explode when their SetFooDeadline methods are called.
|
||||
// It isn't actually used for testing timeouts.
|
||||
const someTimeout = 10 * time.Second
|
||||
const someTimeout = 1 * time.Hour
|
||||
|
||||
func TestConnAndListener(t *testing.T) {
|
||||
for i, network := range []string{"tcp", "unix", "unixpacket"} {
|
||||
|
|
Loading…
Reference in a new issue