Skip test causing gRPC data race in sanitizer build #642
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR skips one specific test in TSAN build because such test triggers some data race within the gRPC library in a very specific scenario.
The "BackEndKvServer E2E: trigger server-side write error" test is purposely written to cause write-errors on Tx RPC server-side implementation by using the bidirectional-streaming API in an unorthodox way, i.e. not reading responses after sending requests and making the Tx call end abruptly on client-side by
grpc::ClientContext
destruction.Repeating this pattern many times triggers write-errors on Tx RPC server-side implementation and allows to check that server-side lifecycle management for Tx calls is OK but seems to result also in a frequent data race detection during sanitizer builds.