-
Notifications
You must be signed in to change notification settings - Fork 332
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
Unregister views to avoid slow oom issue during meter cleanup #2005
Conversation
Hi @skonto. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@skonto: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Unit tests pass locally on my side, need to retest. |
Do we have a reproducer that allows us to more confidently test that we are no longer leaking memory? Can we potentially write a unit(ish) test that makes sure we don't leak memory? |
Codecov Report
@@ Coverage Diff @@
## master #2005 +/- ##
==========================================
+ Coverage 67.15% 67.20% +0.05%
==========================================
Files 214 214
Lines 9091 9102 +11
==========================================
+ Hits 6105 6117 +12
- Misses 2711 2712 +1
+ Partials 275 273 -2
Continue to review full report at Codecov.
|
@markusthoemmes I added a unit test hope that helps. Not sure if there is way to check this better eg. compare actual mem allocations. |
/retest |
@skonto: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@markusthoemmes could you add |
/ok-to-test |
/retest |
Not sure what is wrong here with the unit tests but they pass locally. |
Now I see:
|
/retest |
|
@julz @vagababov @markusthoemmes should this be merged now? I think the failing test should be handled on its own separately. |
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
/assign @evankanderson
For Evan to stamp approval.
@evankanderson gentle ping. |
@evankanderson @vagababov should we merge? wdyth? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evankanderson, skonto The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
…e#2005) * unregister views * add a test * fix string issue * fix * fixes * fixe races in tests * fix exporter issue * stop meter in cleanup * fixes * typo * revert timeout change * fixes * change msg
…e#2005) * unregister views * add a test * fix string issue * fix * fixes * fixe races in tests * fix exporter issue * stop meter in cleanup * fixes * typo * revert timeout change * fixes * change msg
Changes
/kind bug
/cc @evankanderson