[ISSUE-196] Fix flaky test about kerberos #250
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
zuston
force-pushed
the
fix22
branch
4 times, most recently
from
00ff7f1
to
101d38a
Compare
Codecov Report
@@ Coverage Diff @@
## master #250 +/- ##
============================================
- Coverage 59.29% 59.25% -0.04%
+ Complexity 1346 1345 -1
============================================
Files 162 162
Lines 8789 8789
Branches 828 828
============================================
- Hits 5211 5208 -3
- Misses 3311 3313 +2
- Partials 267 268 +1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
jerqi
reviewed
Sep 28, 2022
jerqi
changed the title
jerqi
approved these changes
Sep 29, 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.
What changes were proposed in this pull request?
Fix flaky test about kerberos #196
Why are the changes needed?
Fix flaky test
Does this PR introduce any user-facing change?
No
How was this patch tested?
No need.