Found new dashboard test flakes for:

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

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

— watchflakes

Found new dashboard test flakes for:

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

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

— watchflakes

Found new dashboard test flakes for:

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

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

— watchflakes

Found new dashboard test flakes for:

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

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

— watchflakes

Found new dashboard test flakes for:

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

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

— watchflakes

(attn @ianlancetaylor @neild)

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.

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