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

x/website: Internal Server Error from go-get requests to golang.org #52851

Open
bcmills opened this issue May 11, 2022 · 5 comments
Open

x/website: Internal Server Error from go-get requests to golang.org #52851

bcmills opened this issue May 11, 2022 · 5 comments
Labels
NeedsInvestigation website
Milestone

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented May 11, 2022

            > ! go list -m golang.org/x/text
            [stderr]
            go: unrecognized import path "golang.org/x/text": reading https://golang.org/x/text?go-get=1: 500 Internal Server Error
            go: example.com@v0.0.0 requires
            	golang.org/x/text@v0.1.1-0.20170915032832-14c0d48ead0c+incompatible: unrecognized import path "golang.org/x/text": reading https://golang.org/x/text?go-get=1: 500 Internal Server Error
            [exit status 1]

greplogs -l -e 'https://golang\.org/x/[^?]*\?go-get=1.* 5\d\d ' --since=2021-01-01
2022-05-10T20:13:31-2ecf747/linux-amd64-longtest
2022-05-10T16:17:51-30a2750/linux-386-longtest
2022-05-10T15:33:47-f7209f9/linux-386-longtest
2022-05-04T20:20:28-fbb47e8/linux-amd64-longtest
2022-04-11T02:55:52-a6f6932/linux-386-longtest
2022-02-15T21:18:59-08ed488/linux-386-longtest
2022-01-11T15:23:23-28f2869/linux-386-longtest
2022-01-06T21:38:57-c5540e5/linux-amd64-longtest
2021-11-22T23:09:35-9678f79/linux-386-longtest
2021-11-09T16:55:47-34abc12/linux-386-longtest
2021-10-15T16:57:36-a80e53e/linux-386-longtest
2021-10-08T21:38:44-74abcab/linux-386-longtest
2021-10-04T19:51:37-579ff8b/linux-amd64-longtest
2021-09-24T00:30:36-c90ead9/linux-386-longtest
2021-09-02T13:52:06-a35c5c9/linux-386-longtest
2021-08-28T18:48:37-f4cd001/linux-386-longtest
2021-04-21T13:38:59-4d56576/linux-386-longtest

@gopherbot gopherbot added this to the Unreleased milestone May 11, 2022
@bcmills bcmills added the NeedsInvestigation label May 11, 2022
@bcmills
Copy link
Member Author

@bcmills bcmills commented May 11, 2022

@golang/release: the cluster of status-500 responses yesterday in particular seems a bit worrying. Did those show up in internal monitoring?

@gopherbot
Copy link

@gopherbot gopherbot commented May 11, 2022

Change https://go.dev/cl/405714 mentions this issue: cmd/go: add timestamps to script test output

@dmitshur
Copy link
Contributor

@dmitshur dmitshur commented May 11, 2022

There doesn't appear to be anything abnormal for yesterday at https://console.cloud.google.com/appengine?project=golang-org nor https://console.cloud.google.com/monitoring/uptime?project=golang-org (which you should have access to). However, I am seeing an increased latency as of May 9, 8 pm at https://console.cloud.google.com/monitoring/uptime/go-dev?project=golang-org.

Also CC @jamalc. (The tools team is the the go.dev website owner now.)

gopherbot pushed a commit that referenced this issue May 11, 2022
Go tests don't include timestamps by default, but we would like to
have them in order to correlate builder failures with server and
network logs.

Since many of the Go tests with external network and service
dependencies are script tests for the 'go' command, logging timestamps
here adds a lot of logging value with one simple and very low-risk
change.

For #50541.
For #52490.
For #52545.
For #52851.

Change-Id: If3fa86deb4a216ec6a1abc4e6f4ee9b05030a729
Reviewed-on: https://go-review.googlesource.com/c/go/+/405714
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Auto-Submit: Bryan Mills <bcmills@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Run-TryBot: Bryan Mills <bcmills@google.com>
@bcmills
Copy link
Member Author

@bcmills bcmills commented May 12, 2022

@dmitshur, the uptime charts don't seem detailed enough to surface these errors, and I don't appear to have the right permissions for the /appengine page. (Is there a URL for debug logs somewhere? Or is the /appengine page where the debug logs are supposed to be?)

@bcmills
Copy link
Member Author

@bcmills bcmills commented May 12, 2022

(https://build.golang.org/log/932d64b5e72fd57cce74a37d3c43531068766e0a shows one of these failures with an approximate timestamp of 2022-05-11T19:47:45Z.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation website
Projects
None yet
Development

No branches or pull requests

3 participants