You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Looking at build.golang.org right now, all 4 linux-arm failures are due to TestLookupGoogleSRV flakes:
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.
The text was updated successfully, but these errors were encountered: