-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
WIP release-3.3: test grpc-go 1.22.1 #10952
Conversation
gRPC has moved the transport package to an internal-only directory. This eliminates direct use of the transport package in the stress test in favor of the error code from gRPC that represents a connection problem. https://godoc.org/google.golang.org/grpc/internal/transport is the new location for the package, which says it's not intended to be imported directly. Instead, the maintainers suggested to use the code Unavailable to detect a connection problem. This change slightly reorganizes the stresser test error handling.
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Signed-off-by: Gyuho Lee <gyuhox@gmail.com>
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Otherwise, grpc.DialContext would just return before connection is up. Signed-off-by: Gyuho Lee <gyuhox@gmail.com>
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
9884cd5
to
9cc5474
Compare
Status update unit tests pass when GRPC_GO_REQUIRE_HANDSHAKE=off is defined. This comment seems to outline the issue I am seeing grpc/grpc-go#2636 (comment). "While in the new behavior where HANDSHAKE is required, the client won't sent the request until the HANDSHAKE is done. This results in a deadlock." This seems to be resolved by https://github.com/grpc/grpc-go/pull/2904/commits which will be part of 1.23. Still getting a race/failure with Watch I hope to clear this up soon. My hope is to be able to release a gRPC update only in 3.3 fixing #9956 for release-3.3 which would not change the actual balancer. Then when we feel confident in the new balancer backport. @gyuho thoughts? |
|
Looks like cmux [1] could be causing Watch failures. I will test using [1] grpc/grpc-go#2636 (comment) |
bdeab15
to
471358d
Compare
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Signed-off-by: Gyuho Lee <gyuhox@gmail.com>
d8c6b30
to
99c6dd5
Compare
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
All tests pass I will raise a new clean version to backport. |
This PR is an effort to resolve #9956 for release-3.3.