Most likely a dup of #26988 and/or #27285.

Shouldn't this be part of Go1.11.1? Or are there any workarounds?

Running a CI pipeline is problematic when go test fails on the simplest of files:

package foo
import  _ "net/http"

This problem has been reported several times in several different bugs. We should probably try to concentrate on one issue. CC @bcmills

I'm starting with #27285 because it's easy to reproduce and leads to similar symptoms. I plan to recheck this issue once that one is resolved, in case the underlying cause is the same for both.

Pretty sure this one in particular is a dup of #26988.

Setting the environment variable CGO_ENABLED to 0 fixed it for me.

If you use docker, insert the following before your RUN go test or RUN go build operation:

ENV CGO_ENABLED 0

Pretty sure this one in particular is a dup of #26988.

It's not :(

With go version go1.12.7 linux/amd64, "go build" does not need gcc, but "go test" does.

Having a directory with just one file, "foo.go", with just the lines:

package foo
import _ "net"

results in:

$ go test
# runtime/cgo
exec: "gcc": executable file not found in $PATH

ENV CGO_ENABLED 0 solved it for me

Setting the environment variable CGO_ENABLED to 0 fixed it for me.

If you use docker, insert the following before your RUN go test or RUN go build operation:

ENV CGO_ENABLED 0

This also worked for me, but I did:

RUN CGO_ENABLED=0 go test -run="" /tmp/build/pkg/*

To avoid setting an environment variable.

Thanks jkomyno