Closed daurnimator closed 1 month ago
Are you running Go 1.23?
I am suspecting the underlying implementation for Go 1.23 changed the behavior for this specific test case.
% /usr/local/go/bin/go test ./...
ok github.com/grafana/loki/v3/pkg/storage/chunk/client/gcp 1.762s
% /usr/local/go/bin/go version
go version go1.22.7 darwin/arm64
% go test ./...
--- FAIL: TestTCPErrs (0.11s)
--- FAIL: TestTCPErrs/transport_connect_timeout_exceeded,_retryable (0.04s)
gcs_object_client_test.go:233:
Error Trace: /Users/progers/dev/src/github.com/grafana/loki/pkg/storage/chunk/client/gcp/gcs_object_client_test.go:233
Error: Not equal:
expected: true
actual : false
Test: TestTCPErrs/transport_connect_timeout_exceeded,_retryable
FAIL
FAIL github.com/grafana/loki/v3/pkg/storage/chunk/client/gcp 1.754s
FAIL
% go version
go version go1.23.1 darwin/arm64
Are you running Go 1.23?
Yes
I have put in a fix into the main
branch, along with the 3.2 branch, so 3.2.1 will have this fix.
Describe the bug
TestTCPErrs
failing in Loki 3.2.0 releaseTo Reproduce Steps to reproduce the behavior:
go test ./pkg/storage/chunk/client/gcp/
Expected behavior Tests pass
Environment: ArchLinux build system
Screenshots, Promtail config, or terminal output
Adding a
print
fortc.name
and the error I get: