net/http: TestTransportEventTraceRealDNS fails consistently #17670
Comments
/cc @bradfitz |
Perhaps this is a subset of #17472? |
This test is testing "real DNS" and you don't have real DNS. Change your DNS to 8.8.8.8 or another standards-conformant DNS provider and it'll pass. Or run with |
Ahh, gotcha! Thanks |
I just tripped over a funny version of the problem. I have a Digital Ocean droplet running an image based on their CentOS 7 image. That machine was named foobar.dev.
and
For some reason, when it was unable to resolve dns-should-not-resolve.golang it tried dns-should-not-resolve.golang.dev ( Things in .dev now resolve to My "fix" was to just rename the machine. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version devel +5552d08 Sat Oct 29 18:36:48 2016 +0000 darwin/amd64
tip at 5552d08
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOBIN="/Users/emmanuelodeke/go/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/emmanuelodeke/go"
GORACE=""
GOROOT="/Users/emmanuelodeke/go/src/go.googlesource.com/go"
GOTOOLDIR="/Users/emmanuelodeke/go/src/go.googlesource.com/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/v3/7z434qpx5v3bw0wh8h2myfpw0000gn/T/go-build205502808=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
All pass or a flake in the worst case.
What did you see instead?
Is there something I change? I also tried running the test with
CGO_ENABLED=0 go test -run=TestTransportEventTraceRealDNS
but same results.The text was updated successfully, but these errors were encountered: