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

TestTCPErrs failing in Loki 3.2.0 release #14206

Closed
daurnimator opened this issue Sep 20, 2024 · 4 comments
Closed

TestTCPErrs failing in Loki 3.2.0 release #14206

daurnimator opened this issue Sep 20, 2024 · 4 comments
Assignees

Comments

@daurnimator
Copy link

Describe the bug
TestTCPErrs failing in Loki 3.2.0 release

To Reproduce
Steps to reproduce the behavior:

  1. run go test ./pkg/storage/chunk/client/gcp/

Expected behavior
Tests pass

Environment:
ArchLinux build system

Screenshots, Promtail config, or terminal output

--- FAIL: TestTCPErrs (0.11s)
    --- FAIL: TestTCPErrs/transport_connect_timeout_exceeded,_retryable (0.04s)
        gcs_object_client_test.go:233: 
            	Error Trace:	/build/loki/src/loki-3.2.0/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.250s

Adding a print for tc.name and the error I get:

request took longer than client timeout, not retryable Get "http://127.0.0.1:40385/test-bucket/foo": context deadline exceeded
client timeout exceeded on connect, not retryable Get "http://127.0.0.1:38809/test-bucket/foo": context deadline exceeded
transport connect timeout exceeded, retryable Get "http://127.0.0.1:39235/test-bucket/foo": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
connection is closed server-side before being established Get "http://127.0.0.1:36567/test-bucket/foo": read tcp 127.0.0.1:47866->127.0.0.1:36567: read: connection reset by peer
connection is closed server-side after being established Get "http://127.0.0.1:40381/test-bucket/foo": read tcp 127.0.0.1:36634->127.0.0.1:40381: read: connection reset by p
@paul1r
Copy link
Collaborator

paul1r commented Sep 20, 2024

Are you running Go 1.23?

I am suspecting the underlying implementation for Go 1.23 changed the behavior for this specific test case.

@paul1r
Copy link
Collaborator

paul1r commented Sep 20, 2024



% /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

@daurnimator
Copy link
Author

Are you running Go 1.23?

Yes

@paul1r
Copy link
Collaborator

paul1r commented Sep 23, 2024

I have put in a fix into the main branch, along with the 3.2 branch, so 3.2.1 will have this fix.

@paul1r paul1r closed this as completed Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants