net: TestDialTimeout failures

[gopherbot]

#!watchflakes
post <- pkg == "net" && test == "TestDialTimeout" && `Dial didn't return in an expected time`

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestDialTimeout (1.21s)
    timeout_test.go:83: #7: Dial didn't return in an expected time

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "net" && test == "TestDialTimeout"

2022-12-19 21:45 darwin-amd64-11_0 go@da744b19 net.TestDialTimeout (log)

--- FAIL: TestDialTimeout (1.21s)
    timeout_test.go:83: #7: Dial didn't return in an expected time

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "net" && test == "TestDialTimeout"

2022-12-09 20:04 darwin-amd64-10_15 go@c2a2fbab net.TestDialTimeout (log)

--- FAIL: TestDialTimeout (1.12s)
    timeout_test.go:83: #6: Dial didn't return in an expected time

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "net" && test == "TestDialTimeout"

2023-02-03 19:01 darwin-amd64-12_0 go@cd1fc871 net.TestDialTimeout (log)

--- FAIL: TestDialTimeout (1.00s)
    timeout_test.go:83: #5: Dial didn't return in an expected time

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "net" && test == "TestDialTimeout"

2023-02-04 02:26 darwin-amd64-13 go@82e04653 net.TestDialTimeout (log)

--- FAIL: TestDialTimeout (1.21s)
    timeout_test.go:83: #7: Dial didn't return in an expected time

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "net" && test == "TestDialTimeout"

2023-02-23 06:09 darwin-amd64-12_0 go@ecff9c93 net.TestDialTimeout (log)

--- FAIL: TestDialTimeout (1.00s)
    timeout_test.go:83: #5: Dial didn't return in an expected time

— watchflakes

[bcmills]

(attn @ianlancetaylor @neild)

[ianlancetaylor]

All reported failures are on darwin-amd64. The failures are all tests 5, 6, 7. These tests all set up a dial using a test hook that sleeps for 100 milliseconds and then returns an error (there is no actual call to syscall.Connect). The error occurs when a 1 second timer fires before the dial completes. I don't see any system calls here so the only obvious way that this could fail would be if the 1 second timer fires before the 100 millisecond timeout completes. Not sure how that correlates to darwin-amd64.

[gopherbot]

Change https://go.dev/cl/476356 mentions this issue: net: remove max timeout from TestDialTimeout