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 requ
ill using a vendor directory
>
> On Monday, October 1, 2018 at 6:27:57 PM UTC+2, Mark Rushakoff wrote:
>>
>> https://github.com/golang/go/issues/26794 is "can't run go builds
>> concurrently if they download modules".
>>
>> In that issue, Russ says:
>
