cmd/go: TestScript/mod_list_pseudo fails with "server response: 404 page not found" in AIX #53533
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
OS-AIX
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
The issue is seen in the recent versions of 1.17.X releases, ie., 1.17.11 & 1.17.10 but not in 1.17.9
Not sure about 1.18.X release though.
What operating system and processor architecture are you using (
go env
)?go env
OutputAs part of building go 1.17.11, the test suites are ran and there we see "TestScript/mod_list_pseudo" is failing.
....
ok cmd/compile/internal/types2 6.106s
ok cmd/cover 32.048s
ok cmd/doc 1.434s
ok cmd/fix 20.615s
go test proxy running at GOPROXY=http://127.0.0.1:44088/mod
--- FAIL: TestScript (0.06s)
--- FAIL: TestScript/mod_list_pseudo (1.64s)
script_test.go:253:
# Regression test for golang.org/issue/32715.
# When using $GOPATH/pkg/mod/cache/download as a proxy,
# 'latest' queries should prefer tagged versions over pseudo-versions. (0.655s)
> go mod download github.com/dmitshur-test/modtest5@v0.0.0-20190619020302-197a620e0c9a
> go mod download github.com/dmitshur-test/modtest5@v0.5.0-alpha
> go mod download github.com/dmitshur-test/modtest5@v0.5.0-alpha.0.20190619023908-3da23a9deb9
e
[stderr]
go mod download: github.com/dmitshur-test/modtest5@v0.5.0-alpha.0.20190619023908-3da23a9deb9e
: reading http://127.0.0.1:44088/mod/github.com/dmitshur-test/modtest5/@v/v0.5.0-alpha.0.20190619023908-3
da23a9deb9e.info: 404 Not Found
server response: 404 page not found
[exit status 1]
FAIL: testdata/script/mod_list_pseudo.txt:10: unexpected command failure
FAIL
FAIL cmd/go 723.774s
ok cmd/go/internal/auth 0.056s
The same failure is also seen with 1.17.10 but not in 1.17.9
So I presume some changes that went in 1.17.10 has created this regression.
The text was updated successfully, but these errors were encountered: