Override/disable gRPC call rate meters in test harness driver #5683
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…build dirs This fixes an inconsistency in the scaffold setup.
Ad-hoc API testers need to be able to run the test harness without interference from the production api method call rate meters. This change overrides and disables most call rate meters when the test harness is run from the ApiTestMain driver (no jupiter tests).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ad-hoc API testers need to be able to run the test harness without interference from the production api method call rate meters. This change overrides and disables most call rate meters when the test harness is run from the
ApiTestMaindriver (no jupiter tests).