Giters

yarpc / yarpc-go

A message passing platform for Go

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Transient failure of gRPC TLS test

kriskowal opened this issue · comments

commented

Within vim, testing the gRPC transport’s TLS support reliably fails with connection errors instead of TLS errors, but consistently passes in Docker. There may be a behavior difference between Linux and OS X.

I intend to disable (Skip) TestTLSWithYARPCAndGRPC until we find a resolution.

transport/grpc/logger.go|130| 2019-11-27T15:41:01.320-0800	INFO	started GRPC inbound	{"address": "127.0.0.1:63473"}
transport/grpc/integration_test.go|164| 
|| 	Error Trace:	integration_test.go:164
|| 	            				integration_test.go:150
|| 	            				integration_test.go:406
|| 	            				integration_test.go:148
|| 	Error:      	"code:unavailable message:all SubConns are in TransientFailure, latest connection error: connection closed" does not contain "remote error: tls: bad certificate"
|| 	Test:       	TestTLSWithYARPCAndGRPC/invalid_client_cert
transport/grpc/integration_test.go|164| 
|| 	Error Trace:	integration_test.go:164
|| 	            				integration_test.go:153
|| 	            				integration_test.go:406
|| 	            				integration_test.go:148
|| 	Error:      	"rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection closed" does not contain "remote error: tls: bad certificate"
|| 	Test:       	TestTLSWithYARPCAndGRPC/invalid_client_cert