-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[1.20] ResourceStore: fix segfault and update tests #4535
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
[1.20] ResourceStore: fix segfault and update tests #4535
Conversation
before, it was possible to segfault when a WatcherForResource was called followed by a Get as we didn't check that the resource was actually put. Fix this Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
We need to specifically register "Describe" functions, but ginkgo doesn't allow us to register multiple ones. Wrap different functionality in different Contexts so they all run. Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
|
/lgtm |
Codecov Report
@@ Coverage Diff @@
## release-1.20 #4535 +/- ##
================================================
+ Coverage 40.54% 40.63% +0.08%
================================================
Files 117 117
Lines 9422 9436 +14
================================================
+ Hits 3820 3834 +14
+ Misses 5173 5172 -1
- Partials 429 430 +1 |
saschagrunert
left a comment
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
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, mrunalp, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
What type of PR is this?
What this PR does / why we need it:
There is a chance that a WatcherForResource() followed by a Get() would cause cri-o to segfault. Fix this
also extend the test suite to add a test for this and another situation, as well as move around the tests so they're all run
Which issue(s) this PR fixes:
Special notes for your reviewer:
cherry-pick of #4530
Does this PR introduce a user-facing change?