-
Notifications
You must be signed in to change notification settings - Fork 867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: flakey TestWriteBackToInformer test #2621
fix: flakey TestWriteBackToInformer test #2621
Conversation
Signed-off-by: zachaller <[email protected]>
Codecov ReportBase: 81.50% // Head: 81.52% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #2621 +/- ##
==========================================
+ Coverage 81.50% 81.52% +0.01%
==========================================
Files 131 131
Lines 19562 19562
==========================================
+ Hits 15944 15947 +3
+ Misses 2798 2795 -3
Partials 820 820
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Signed-off-by: zachaller <[email protected]>
Signed-off-by: zachaller <[email protected]>
Signed-off-by: zachaller <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a comment.
Otherwise LGTM
Signed-off-by: zachaller <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This fixes the flakey unit test
TestWriteBackToInformer
I was able to easily reproduce the flake buy putting the test into a loop, when I switched out the code to use json marshaling it 3000 iterations passed.This is possibly somewhat a hack solution for how we are using the fake client with informers. There could also be a bug upstream in k8s fake client.