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

build: unrecognized failures on linux-ppc64-buildlet #55314

Open
gopherbot opened this issue Sep 21, 2022 · 2 comments
Open

build: unrecognized failures on linux-ppc64-buildlet #55314

gopherbot opened this issue Sep 21, 2022 · 2 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@gopherbot
Copy link

#!watchflakes
post <- builder == "linux-ppc64-buildlet" && pkg == "" && test == ""

Issue created automatically to collect these failures.

Example (log):

Test "go_test:cmd/go/internal/mvs" ran over 40m0s limit (40m0.001064589s); saw output:

XXXBANNERXXX:Test execution environment.
# GOARCH: ppc64
# CPU: POWER8
# GOOS: linux
# OS Version: Linux 4.4.0-130-powerpc64-smp #156-Ubuntu SMP Thu Jun 14 09:28:49 UTC 2018 ppc64

watchflakes

@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Sep 21, 2022
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- builder == "linux-ppc64-buildlet" && pkg == "" && test == ""
2022-08-11 17:23 linux-ppc64-buildlet go@dfbecc06 (log)
Test "go_test:cmd/go/internal/mvs" ran over 40m0s limit (40m0.001064589s); saw output:

XXXBANNERXXX:Test execution environment.
# GOARCH: ppc64
# CPU: POWER8
# GOOS: linux
# OS Version: Linux 4.4.0-130-powerpc64-smp #156-Ubuntu SMP Thu Jun 14 09:28:49 UTC 2018 ppc64
2022-09-02 20:03 linux-ppc64-buildlet website@1358680b go@bd5595d7 (log)
../../../../pkg/mod/cloud.google.com/go@v0.88.0/internal/annotate.go:20:2: google.golang.org/api@v0.51.0: read "https:/proxy.golang.org/@v/v0.51.0.zip": read tcp 172.17.0.6:51720->142.251.211.240:443: read: connection reset by peer
../../../../pkg/mod/cloud.google.com/go/datastore@v1.2.0/query.go:29:2: google.golang.org/api@v0.51.0: read "https:/proxy.golang.org/@v/v0.51.0.zip": read tcp 172.17.0.6:51720->142.251.211.240:443: read: connection reset by peer
../../../../pkg/mod/cloud.google.com/go/datastore@v1.2.0/datastore.go:26:2: google.golang.org/api@v0.51.0: read "https:/proxy.golang.org/@v/v0.51.0.zip": read tcp 172.17.0.6:51720->142.251.211.240:443: read: connection reset by peer
../../../../pkg/mod/cloud.google.com/go/datastore@v1.2.0/datastore.go:27:2: google.golang.org/api@v0.51.0: read "https:/proxy.golang.org/@v/v0.51.0.zip": read tcp 172.17.0.6:51720->142.251.211.240:443: read: connection reset by peer
../../../../pkg/mod/cloud.google.com/go/datastore@v1.2.0/datastore.go:28:2: google.golang.org/api@v0.51.0: read "https:/proxy.golang.org/@v/v0.51.0.zip": read tcp 172.17.0.6:51720->142.251.211.240:443: read: connection reset by peer
../../../../pkg/mod/cloud.google.com/go@v0.88.0/longrunning/autogen/operations_client.go:29:2: google.golang.org/api@v0.51.0: read "https:/proxy.golang.org/@v/v0.51.0.zip": read tcp 172.17.0.6:51720->142.251.211.240:443: read: connection reset by peer
../../../../pkg/mod/cloud.google.com/go/storage@v1.10.0/acl.go:24:2: google.golang.org/api@v0.51.0: read "https:/proxy.golang.org/@v/v0.51.0.zip": read tcp 172.17.0.6:51720->142.251.211.240:443: read: connection reset by peer
../../../../pkg/mod/cloud.google.com/go/storage@v1.10.0/storage.go:47:2: google.golang.org/api@v0.51.0: read "https:/proxy.golang.org/@v/v0.51.0.zip": read tcp 172.17.0.6:51720->142.251.211.240:443: read: connection reset by peer
cmd/versionprune/main.go:16:2: google.golang.org/api@v0.51.0: read "https:/proxy.golang.org/@v/v0.51.0.zip": read tcp 172.17.0.6:51720->142.251.211.240:443: read: connection reset by peer

watchflakes

@bcmills
Copy link
Contributor

bcmills commented Sep 21, 2022

Looks like #53201 plus a network flake.

@seankhliao seankhliao added this to the Unplanned milestone Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: Active
Development

No branches or pull requests

3 participants