x/build: linux-loong64-3a5000 persistently failing to build x/arch and x/net due to i/o timeout dialing proxy.golang.org

[bcmills]

#!watchflakes
post <- builder == "linux-loong64-3a5000" && log ~ `proxy\.golang\.org.*: i/o timeout`

https://build.golang.org/log/94991b7187c612dbbf72b6c15a6b8042c1b13f0f:

go: downloading rsc.io/pdf v0.1.1
arm/armspec/spec.go:34:2: rsc.io/pdf@v0.1.1: Get "https://proxy.golang.org/rsc.io/pdf/@v/v0.1.1.zip": dial tcp 142.251.43.17:443: i/o timeout

https://build.golang.org/log/e29d99548ed4fe041384e5c0bc53608a46dace6e:

go: downloading golang.org/x/sys v0.12.0
go: downloading golang.org/x/text v0.13.0
go: downloading golang.org/x/term v0.12.0
go: downloading golang.org/x/crypto v0.13.0
html/charset/charset.go:20:2: golang.org/x/text@v0.13.0: Get "https://proxy.golang.org/golang.org/x/text/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
html/charset/charset.go:21:2: golang.org/x/text@v0.13.0: Get "https://proxy.golang.org/golang.org/x/text/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
html/charset/charset.go:22:2: golang.org/x/text@v0.13.0: Get "https://proxy.golang.org/golang.org/x/text/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
html/charset/charset.go:23:2: golang.org/x/text@v0.13.0: Get "https://proxy.golang.org/golang.org/x/text/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
idna/idna10.0.0.go:26:2: golang.org/x/text@v0.13.0: Get "https://proxy.golang.org/golang.org/x/text/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
idna/idna10.0.0.go:27:2: golang.org/x/text@v0.13.0: Get "https://proxy.golang.org/golang.org/x/text/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
idna/idna10.0.0.go:28:2: golang.org/x/text@v0.13.0: Get "https://proxy.golang.org/golang.org/x/text/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
http2/h2i/h2i.go:42:2: golang.org/x/term@v0.12.0: Get "https://proxy.golang.org/golang.org/x/term/@v/v0.12.0.zip": dial tcp 142.251.42.241:443: i/o timeout
internal/socket/cmsghdr_unix.go:10:8: golang.org/x/sys@v0.12.0: Get "https://proxy.golang.org/golang.org/x/sys/@v/v0.12.0.zip": dial tcp 142.251.42.241:443: i/o timeout
internal/quic/packet_protection.go:18:2: golang.org/x/crypto@v0.13.0: Get "https://proxy.golang.org/golang.org/x/crypto/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
internal/quic/packet_protection.go:19:2: golang.org/x/crypto@v0.13.0: Get "https://proxy.golang.org/golang.org/x/crypto/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
internal/quic/packet_protection.go:20:2: golang.org/x/crypto@v0.13.0: Get "https://proxy.golang.org/golang.org/x/crypto/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout
internal/quic/packet_protection.go:21:2: golang.org/x/crypto@v0.13.0: Get "https://proxy.golang.org/golang.org/x/crypto/@v/v0.13.0.zip": dial tcp 142.251.42.241:443: i/o timeout

@golang/loong64: does this builder perhaps need a different GOPROXY configuration?

[abner-chenc]

Sorry, I have updated the network proxy and tested and everything is fine.

[bcmills]

@abner-chenc, thanks, but it looks like the builder is still failing in the same way: https://build.golang.org/log/2be2c8f0e5c59445b6d94dfed2420dd2e48687b7

[xen0n]

@abner-chenc: I see there's no GOPROXY in the builder env, so there's still (real) possibility that the connection to the official gomod proxy's gonna be fragile.

If possible, you could try GOPROXY=https://goproxy.cn,direct which is a well-known proxy service (kindly provided by my previous employer and reliably accelerating downloads for years already).

[abner-chenc]

@abner-chenc: I see there's no GOPROXY in the builder env, so there's still (real) possibility that the connection to the official gomod proxy's gonna be fragile.

If possible, you could try GOPROXY=https://goproxy.cn,direct which is a well-known proxy service (kindly provided by my previous employer and reliably accelerating downloads for years already).

Thanks， I have configured the environment variable GOPROXY=https://goproxy.cn,direct in the buildlet service

[xen0n]

I can confirm the proxy setting is in effect, and the dashboard indicates the problem is gone. I think the issue can be closed?