#729: Ignoring the flipper #735
Merged
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
andrzejj0
force-pushed
the
issue-729-flipper
branch
from
20544fd
to
156ee09
Compare
…iling and not as part of integration testing
andrzejj0
force-pushed
the
issue-729-flipper
branch
from
156ee09
to
8163f4d
Compare
|
Added a more elaborate description. |
slawekjaranowski
approved these changes
Oct 4, 2022
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.
This test should be used for profiling and not as part of integration testing. Caching rule resolution is a good start, but the actual performance depends on the machine and conditions of the cluster, but tests should not really depend on the volatile cluster state.