I found a race condition which results in a segfault - go test -count 1000 ./... without 0a67846 manages to reproduce the issue very reliably.
Ideally, I'd like to handle the error case of cmd.Start() more elegantly (eg. sending a signal to started children and waiting for them to terminate), but this will do for now.
I found a race condition which results in a segfault -
go test -count 1000 ./...without0a67846manages to reproduce the issue very reliably.Ideally, I'd like to handle the error case of
cmd.Start()more elegantly (eg. sending a signal to started children and waiting for them to terminate), but this will do for now.