-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/build: unexpected EOF with GOPROXY forwarding #58710
Labels
Builders
x/build issues (builders, bots, dashboards)
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
gopherbot
added
the
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
label
Feb 24, 2023
cherrymui
changed the title
go test -timeout=50m0s ./...: unrecognized failures
x/website: network flaky in reading internal site
Feb 24, 2023
Found new dashboard test flakes for:
2023-02-23 15:59 linux-amd64-longtest website@9033d874 go@612c00bf (log)
|
This was referenced Feb 24, 2023
Found new dashboard test flakes for:
2023-02-22 15:48 linux-amd64 website@f2bd60d5 go@c17f8057 (log)
2023-02-23 15:59 linux-amd64-nocgo website@9033d874 go@0fa9ba8a (log)
2023-02-23 21:19 linux-amd64-bullseye pkgsite-metrics@ee44c149 go@f60a2a9c (log)
|
Found new dashboard test flakes for:
2023-02-27 18:03 linux-arm64-longtest pkgsite-metrics@3003b876 go@1e0c32cc (log)
|
CC @jamalc |
Not sure these are actionable. They look like timeouts from downloading modules from the proxy. Can we ignore these types of flakes? |
findleyr
changed the title
x/website: network flaky in reading internal site
x/build: unexpected EOF with GOPROXY forwarding
Apr 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Builders
x/build issues (builders, bots, dashboards)
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: