-
Notifications
You must be signed in to change notification settings - Fork 118
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
Fix FVT runtime count issue #285
Conversation
bf40ad4
to
74e0e45
Compare
Fix FVT runtime count issue by making torchserve as cluster serving runtime as default, similar to other out-of-the-box runtimes Signed-off-by: Chin Huang <[email protected]>
74e0e45
to
b12b93e
Compare
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
/assign @njhill |
@njhill -- when you get a chance, please add your |
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.
Thanks @chinhuang007
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chinhuang007, ckadner, njhill, rafvasq The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fix FVT runtime count issue by making torchserve as cluster serving runtime as default, similar to other out-of-the-box runtimes
Signed-off-by: Chin Huang [email protected]
Motivation
Make FVT working in the default cluster scoped mode
Modifications
Change torchserve-0.x to be a ClusterRuntime
Add a line to e2e FVT to disable torchserve-0.x, similar to github actions
Result
FVT working in cluster scoped mode
e2e working