Closed bits01 closed 6 years ago
Yes, this is a known regression upstream in cmd/go
in Go 1.10. It might get fixed in Go 1.10.1.
See https://github.com/golang/go/issues/23818 and https://github.com/golang/go/issues/23797.
Thanks for reporting this anyway.
Thank you, appreciate your prompt reply.
Any ideas why? This is with go 1.10, not sure whether it has anything to do with the new build cache.