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

gRPC client do not return immediately after receiving a status #3018

Open
pablochacin opened this issue Apr 12, 2023 · 1 comment
Open

gRPC client do not return immediately after receiving a status #3018

pablochacin opened this issue Apr 12, 2023 · 1 comment

Comments

@pablochacin
Copy link

Brief summary

When testing the injection of faults in grpc protocol using the xk6-disruptor extension I notice the requests made with the k6 grpc client did not return immediately after receiving an error status but waited until the timeout specified in the invoke options.

This behavior differs from the behavior observed with for example grpc-client-cli which returns immediately on receiving an error.

k6 version

0.42

OS

Linux

Docker version and image (if applicable)

No response

Steps to reproduce the problem

Follow the instructions) for injecting errors using the xk6-disruptor extension.

Note: Using the grpcnbin RandomError method will not show this as it returns an empty message after setting the status code.

Expected behaviour

The invoke function returns immediately regardless of the timeout specified when invoking the grpc method.

Actual behaviour

The invoke method waits until the timeout is expired and then returns the fault.

@pablochacin pablochacin changed the title gRPC client waits for message after receiving a status Apr 12, 2023
@Azhovan
Copy link
Contributor

Azhovan commented Dec 29, 2023

/Assign ✋🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants