Go version

go1.25 development branch (multiple commits including d184f8dc0)

Output of go env in your module/workspace:

GOARCH="ppc64le"
GOOS="linux"
GOVERSION="go1.25"
GOHOSTARCH="ppc64le"
GOHOSTOS="linux"

# Running on Power8 Little-Endian (ppc64le) builder: gotip-linux-ppc64le_power8

What did you do?

Observed persistent test failures on the gotip-linux-ppc64le_power8 builder in:

cmd/go/internal/modfetch/codehost.TestLatest

cmd/go/internal/modfetch/codehost.TestReadFile

cmd/go/internal/modfetch/codehost.TestReadZip

What did you see happen?

Most failed subtests are under the gitrepo-sha256/... prefix, e.g.:

TestReadFile/gitrepo-sha256/v2.3.4/another.txt

TestReadZip/gitrepo-sha256/v2.3.4/

TestLatest/gitrepo-sha256

These failures have occurred across multiple commits in the Go 1.25 development cycle, including but not limited to:

d184f8dc0 (June 7, 2025)

What did you expect to see?

All tests to pass, as they do on other architectures and platforms.

Comment From: jkrishmys

I ran the same cmd/go/internal/modfetch/codehost tests locally on a Power8 LE (ppc64le) system using:

  • go version devel go1.25-...
  • git version 2.47.0

All gitrepo-sha256 subtests passed locally, including TestReadFile, TestReadZip, and TestLatest.

This may suggest that the failures observed on the gotip-linux-ppc64le_power8 builder are specific to the CI environment — possibly due to an outdated Git version or file system characteristics. I will investigate it further.

Comment From: jkrishmys

cc @golang/ppc64

Comment From: jkrishmys

After reviewing the test logs for TestLatest/gitrepo-sha256, the failure is due to Git 2.25.1 on Ubuntu 20.04 running on Power8le, not supporting --object-format=sha256 (introduced in Git 2.29.0). The git init --object-format=sha256 command fails with exit status 129, causing git ls-remote to return an HTTP 500 error. The OSU team rebooted the VM, but the issue persists, as expected, since it’s tied to the Git version.

Comment From: jkrishmys

As a short term fix git 2.49.0 was installed by the OSU team, the issue still persisted. Then the container image was updated to use the updated version. Now the build tests are successful.