-
Notifications
You must be signed in to change notification settings - Fork 267
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 AI Runtime test case #197
Conversation
@@ -67,6 +68,9 @@ def _valid_config(self): | |||
), "Model uri must be in `repo/name` format." | |||
assert self.bucket_name is None, "Bucket name is empty in HuggingFace." | |||
assert self.model_name is not None, "Model name is not set." | |||
assert self.hf_api.repo_exists( |
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.
this is the remote request? if hugging face repo is not accessible from CN machines, does it still work?
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.
I expect this network issue to be bypassed using the HF_ENDPOINT
env setting
@@ -70,10 +70,10 @@ def __init__(self, model_uri): | |||
|
|||
def _valid_config(self): | |||
assert ( | |||
self.bucket_name is not None or self.bucket_name == "" | |||
self.bucket_name is not None and self.bucket_name != "" |
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.
Let's split the feature the CI test in separate PRs in future
* test: add metrics test case * fix&test: fix assert bucket name path logic * add hf repo not exist valid in _valid_config * test: add test case about huggingface downloader * style format and linter * ci: add python test * format
Pull Request Description
Add test case about AI Runtime:
Related Issues
Resolves: #133
Important: Before submitting, please complete the description above and review the checklist below.
Contribution Guidelines (Expand for Details)
We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:
Pull Request Title Format
Your PR title should start with one of these prefixes to indicate the nature of the change:
[Bug]
: Corrections to existing functionality[CI]
: Changes to build process or CI pipeline[Docs]
: Updates or additions to documentation[API]
: Modifications to aibrix's API or interface[CLI]
: Changes or additions to the Command Line Interface[Misc]
: For changes not covered above (use sparingly)Note: For changes spanning multiple categories, use multiple prefixes in order of importance.
Submission Checklist
By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.