It's great that in steady state, go build produces no output on success. However, the lack of feedback as to when go build has finished downloading all its dependencies makes it hard to diagnose whether a long invocation of go build is due to compilation or a network issue. This can be especially important in a CI environment where there is often no cache. While it's possible to run go build with -x or -v to get this information, it's often much more information than is needed.
The behavior I would like to see is that if go build downloads any modules, it prints a log line at the end of the download phase to indicate that the downloads have finished and the build has started. If go build does not download any modules, it would not output anything new.
What version of Go are you using (go version)?
$ go version
go version go1.14.4 linux/amd64
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?