Closed bcmills closed 1 year ago
Marking as release-blocker because this failure mode is new during the Go 1.20 cycle and darwin/arm64
is a first class port.
There is an issue about fork/exec on macOS #53863 , which looks like a kernel issue. I wonder if this has any connection with that.
I wonder if this has any connection with that.
That is plausible, but I think it would be a little surprising given the timing..? That issue affects back to at least Go 1.18.1, but the two failures in the logs are both recent and (so far) only on the main branch.
Found new matching dashboard test flakes for:
#!watchflakes
post <- `^SIGABRT: abort` && `goroutine \d+ \[running\]:\n(.+\n\t.+\n)*syscall\.StartProcess`
Found new dashboard test flakes for:
#!watchflakes
post <- `^SIGABRT: abort` && `goroutine \d+ \[running\]:\n(.+\n\t.+\n)*syscall\.StartProcess`
Timed out in state WaitingForInfo. Closing.
(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)
Reopening because this is still happening. I'm not sure if we have enough extra data to do anything about it yet.
Is this still happening? watchflakes hasn't updated this issue.
watchflakes hasn't updated this issue since October 4th. Closing for now.
greplogs -l -e '^SIGABRT: abort(?:.*\n)*goroutine \d+ \[running\]:\n(?:.+\n\t.+\n)*syscall\.StartProcess' --since=2022-01-01
2022-09-06T22:23:43-c83e1b6/darwin-arm64-12 2022-09-03T06:26:16-9fc09d2/darwin-arm64-12attn @golang/runtime, @golang/darwin