I’m trying to move our builds to 2.0, and currently experiencing an intermittent issue with
go build. Probably about half the time, my builds fail with
/usr/local/go/pkg/tool/linux_amd64/link: signal: killed when building a go package using
go test -v -race ./.... Usually this only affects one package, but not always the same one. In my most recent build, it affected two separate packages.
This seems likely to be and OOM problem, but I don’t have the same tools to debug this as in 1.0, where a snapshot of system RAM was placed into the artifacts.