-
Notifications
You must be signed in to change notification settings - Fork 200
Closed
Labels
test serverRelated to the test serverRelated to the test server
Description
Expected Behavior
Calling describe on the workflow should return a valid result.
Actual Behavior
Calling describe on the workflow sometimes results in a GRPC exception being thrown.
io.grpc.StatusRuntimeException: UNKNOWN
at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:271)
at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:252)
at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:165)
at io.temporal.api.workflowservice.v1.WorkflowServiceGrpc$WorkflowServiceBlockingStub.describeWorkflowExecution(WorkflowServiceGrpc.java:5523)
Steps to Reproduce the Problem
There are not reliable repro steps. The issue is intermittent.
In a JUnit test,
- Set up a
TestWorkflowEnvironment. This is being done in a@BeforeClassmethod in a base class for the unit test class. All instances are stored in class variables for the life of the test. It's not clear to me if the static/class methods/variables are playing a role here or not. - In a
@Beforemethod on the class with the unit tests,
- Start a workflow. This is done indirectly in that our test is calling a GRPC endpoint that is also running inside the test which starts a workflow. However, the starting of the workflow is done synchronously back to the caller. It's not clear to me that the indirection here matters.
- Call DescribeWorkflowExecution using the workflow ID that was used in the previous step
Specifications
- Version: 1.27.1
- Platform: Linux
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
test serverRelated to the test serverRelated to the test server