-
Notifications
You must be signed in to change notification settings - Fork 363
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
[Enhance] Add runner test case. #631
[Enhance] Add runner test case. #631
Conversation
Codecov ReportBase: 78.45% // Head: 78.58% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #631 +/- ##
==========================================
+ Coverage 78.45% 78.58% +0.12%
==========================================
Files 126 128 +2
Lines 9141 9283 +142
Branches 1818 1834 +16
==========================================
+ Hits 7172 7295 +123
- Misses 1656 1672 +16
- Partials 313 316 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Co-authored-by: Zaida Zhou <58739961+zhouzaida@users.noreply.github.com>
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
All unit tests need to build runner could inherit
TestRunnerTestCase
.Modification
Runner
instance,RunnerTestCase
provides a simple way to build runner with iter based or epoch-based config.Runner
will leave a lot of global variable,RunnerTestCase
will clean then after each unit test.RunnerTestCase
will deinitialize the distributed enviroment.Registry
instance likeMODELS
andHOOKS
are also global variables,RunnerTestCase
will also clean them after each unit test,BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist