fix(processbaseline): evaluator bench test#17071
Conversation
Signed-off-by: Tomasz Janiszewski <tomek@redhat.com>
|
Images are ready for the commit at 4799ea6. To use with deploy scripts, first |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #17071 +/- ##
==========================================
- Coverage 48.80% 48.79% -0.01%
==========================================
Files 2707 2711 +4
Lines 202201 202272 +71
==========================================
+ Hits 98679 98694 +15
- Misses 95752 95795 +43
- Partials 7770 7783 +13
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:
|
|
@janisz: 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
Currently the db object is created once for all subtests. This results in growing dataset with every run making it impossible to set
countgreater than 1 as it will increase data for every subtests making benchmark slower with every next run causing high deviation in results and making them harder to compare. This PR moves db creation into a subtest where it will be used and teardown after that subtest.Spotted on:
User-facing documentation
Testing and quality
Automated testing
How I validated my change