#!watchflakes
post <- goos == "darwin" && log ~ `os/exec\.\(\*Cmd\)\.awaitGoroutines` && log ~ `internal/poll\.\(\*pollDesc\)\.waitRead` &&
!(builder ~ `(gotip|go1\.\d\d)-` && date < "2024-01-18")
Many of these bugs have been worked around by explicitly canceling (or adding a timeout to) the stuck read.
A few other issues may be related but don't (or didn't) include goroutine dumps for the stuck process: they may or may not be due to this failure mode.
We have been tracking a long-running bug on macOS (
darwin) in #54461 (comment). That issue title doesn't accurately capture the widespread nature of the problem, nor its defining symptom or suspected root cause; so, I am filing a new issue for it.On macOS, we see a pattern of test failures with the following characteristics:
readoperation on a pipe.Many of these bugs have been worked around by explicitly canceling (or adding a timeout to) the stuck read.
The issues with this symptom have included:
A few other issues may be related but don't (or didn't) include goroutine dumps for the stuck process: they may or may not be due to this failure mode.
subprogram failed: exit status 1afterWaiting for exit...#61595context deadline exceededondarwin#63731signal: killedon darwin #64110context deadline exceededon darwin #64269darwin#64700Given the symptoms, it seems likely to me that this is either a bug in
internal/poll, or a bug in the macOS platform that we have somehow started to trigger.Note that #61779 was bisected specifically to https://go.dev/cl/420334.