Re: [go-nuts] How can I identify the default value of the -p build flag?

Thanks. That confirms that Go thinks there are 36 CPUs available in that environment. I'm still a bit surprised that there's no way to invoke the go executable to get the value of runtime.NumCPU. A quick grep through src/cmd looks like it isn't directly exposed anywhere. I might file an issue

Re: [go-nuts] How can I identify the default value of the -p build flag?

On Fri, Nov 2, 2018 at 2:29 PM, wrote: > > This is somewhat an XY problem, so let me preface with the X: > > We infrequently see `/usr/local/go/pkg/tool/linux_amd64/link: signal: > killed` when running `go test` for our project on CircleCI, running Go > 1.11.1. > > As far as I can tell, that

[go-nuts] How can I identify the default value of the -p build flag?

This is somewhat an XY problem, so let me preface with the X: We infrequently see `/usr/local/go/pkg/tool/linux_amd64/link: signal: killed` when running `go test` for our project on CircleCI, running Go 1.11.1. As far as I can tell, that killed signal is due to OOMing. The comment at