refactor: simplify custom registry usage in metrics tracker#16772
refactor: simplify custom registry usage in metrics tracker#16772parametalol merged 1 commit intomasterfrom
Conversation
|
Images are ready for the commit at 35e895a. To use with deploy scripts, first |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #16772 +/- ##
=======================================
Coverage 48.80% 48.80%
=======================================
Files 2679 2680 +1
Lines 200331 200342 +11
=======================================
+ Hits 97766 97780 +14
+ Misses 94954 94953 -1
+ Partials 7611 7609 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@parametalol: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
Description
Let's remove the registry factory from the constructor signature, as the tests can access the internal tracker field to override the factory for testing purposes.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
CI