-
Notifications
You must be signed in to change notification settings - Fork 193
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: use update instead of patch to set pod's role #8865
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8865 +/- ##
==========================================
+ Coverage 60.16% 60.35% +0.19%
==========================================
Files 382 382
Lines 46293 46293
==========================================
+ Hits 27850 27938 +88
+ Misses 15771 15688 -83
+ Partials 2672 2667 -5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@@ -123,6 +123,44 @@ var _ = Describe("pod role label event handler test", func() { | |||
return nil | |||
}).Times(1) | |||
Expect(handler.Handle(cli, reqCtx, nil, event)).Should(Succeed()) | |||
|
|||
By("read a stale pod") |
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.
Only explicitly mocked update conflicts are present, not a stale read scenario.
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.
By the way, such test cases have no practical significance.
No description provided.