Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net: TestLookupGoogleSRV flaky on linux-arm bot #14997

Closed
mdempsky opened this issue Mar 28, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@mdempsky
Copy link
Member

commented Mar 28, 2016

Looking at build.golang.org right now, all 4 linux-arm failures are due to TestLookupGoogleSRV flakes:

--- FAIL: TestLookupGoogleSRV (20.05s)
    lookup_test.go:71: lookup _xmpp-server._tcp.google.com on 10.1.31.38:53: no such host
FAIL
FAIL    net 22.518s

http://build.golang.org/log/18b91c9dd84cfa397ae48f92f5806eb64be62d41
http://build.golang.org/log/31c93edec34c46a3b140db465f905f2412b8ef2f
http://build.golang.org/log/afede4adbc79168d91a430d5033cbd9d962d2729
http://build.golang.org/log/e6e72e6ad1f44c4ecd87884374d964bb8497582f

This is also causing trybot flakes; e.g., I had linux-arm flakes on golang.org/cl/21231 and golang.org/cl/21232.

@bradfitz

This comment has been minimized.

Copy link
Member

commented Mar 29, 2016

The scaleway ARM builders have:

# cat /etc/resolv.conf  
domain cloud.scaleway.com
search cloud.scaleway.com
nameserver 10.1.31.38
nameserver 10.1.31.39

Which explains the error message.

I guess that DNS server just sucks (is flaky).

Maybe the external net tests should hard-code 8.8.8.8?

@mdempsky

This comment has been minimized.

Copy link
Member Author

commented Mar 29, 2016

I feel like it should be reasonable for tests to assume /etc/resolv.conf points to reliable DNS servers. What about just configuring the Scaleway ARM VMs to use "nameserver 8.8.8.8" in their /etc/resolv.conf instead of changing any tests?

We should probably also warn Scaleway that their DNS servers appear unreliable.

@bradfitz

This comment has been minimized.

Copy link
Member

commented Mar 29, 2016

Done. Sent https://go-review.googlesource.com/21194 and deployed.

@golang golang locked and limited conversation to collaborators Mar 29, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.