Re: [go-nuts] Re: Is it safe to run go build in parallel?

2018-10-11 Thread Yulrizka
Ok, to give some update apparently our Makefile uses `build -i` where it tries to install package dependency. This explains the conflicted `.a` files. It was there before GOCACHE to speed up `go build` Thanks for the help! On Wednesday, October 10, 2018 at 9:40:28 PM UTC+2, Yulrizka wrote: >

Re: [go-nuts] Re: Is it safe to run go build in parallel?

2018-10-10 Thread Yulrizka
It seems that after searching in google, I found couple of similar issue: most of them are related to parallel build with "GNU parallel" which is in our case as well. https://github.com/gravitational/teleport/issues/1708 https://github.com/grpc/grpc-go/issues/368

Re: [go-nuts] Re: Is it safe to run go build in parallel?

2018-10-01 Thread Mark Rushakoff
I saw that you wrote > The reason that I'm using shared GOPATH for this Jenkins step/job is that to now download the packages in `pkg/mod`. And I thought that meant you were using modules. Discussion in https://github.com/golang/go/issues/26677 says that the build cache is explicitly safe, but

[go-nuts] Re: Is it safe to run go build in parallel?

2018-10-01 Thread Yulrizka
Hi Mark, what I find interesting is that I haven't enable go module yet. As you can see in the errors that I'm still 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 >

[go-nuts] Re: Is it safe to run go build in parallel?

2018-10-01 Thread mark
https://github.com/golang/go/issues/26794 is "can't run go builds concurrently if they download modules". In that issue, Russ says: > There is a plan to make downloading of modules by parallel go commands safe but we haven't done that yet. On Monday, October 1, 2018 at 8:43:00 AM UTC-7,