-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[CI] Add torch1.13 checking in CI #2331
Conversation
Codecov ReportBase: 88.97% // Head: 88.97% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #2331 +/- ##
=======================================
Coverage 88.97% 88.97%
=======================================
Files 146 146
Lines 8746 8746
Branches 1474 1474
=======================================
Hits 7782 7782
Misses 722 722
Partials 242 242
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. |
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.
please relate open-mmlab/mmcv#2405
add torch1.13 in ci remove coverage and fix cuda version
add torch1.13 in ci remove coverage and fix cuda version
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
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
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