-
Notifications
You must be signed in to change notification settings - Fork 863
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
Make handler tests callable with pytest #2173
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2173 +/- ##
===========================================
+ Coverage 53.37% 71.45% +18.07%
===========================================
Files 71 73 +2
Lines 3226 3296 +70
Branches 57 57
===========================================
+ Hits 1722 2355 +633
+ Misses 1504 941 -563
... and 12 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
will increase coverage by 18.03%.
:O
…with old weights version on gpu
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.
@mreso Could you please point to the code for integration with TS sanity .
Also, could you please attach the sanity logs to the PR
@ankithagunapal Sure, integration point is here: serve/ts_scripts/backend_utils.py Line 17 in 3f5d4a5
This is output from
Let me know if you need full log. |
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
Description
This PR refactors the torch_handler unit tests to make them callable with pytest and integrates them into torchserve_sanity.py
Fixes #(issue)
1667 (partially)
Type of change
Please delete options that are not relevant.
Feature/Issue validation/testing
Please describe the Unit or Integration tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.
Test A
Logs for Test A
Test B
Logs for Test B
Checklist: