-
Notifications
You must be signed in to change notification settings - Fork 206
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 abi #460
Fix abi #460
Conversation
…history in KV cache
|
||
import os | ||
build_dir = os.getenv('GENAI_BUILD_DIR', 'build') | ||
ov_tokenizers_path = f'{build_dir}/openvino_tokenizers/src/' |
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.
can we use relative path instead?
E.g. tokenizers, genai and python files are copies to the same directory where we can find tokenizer.so relatively to python files.
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.
Yes. To do the same in C++ I'd need a path to the current library. Does openvino have have a function for that or an implementation I could copy?
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.
@@ -33,7 +33,7 @@ jobs: | |||
echo "$models" | while read -r model_name model_path; do | |||
optimum-cli export openvino --trust-remote-code --weight-format fp16 --model "$model_name" "$model_path" | |||
done | |||
python -m pytest test_generate_api.py | |||
GENAI_BUILD_DIR=../../build python -m pytest test_generate_api.py |
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.
tests are example of user code.
users should not know about tokenizers, etc and that some vars need to set, except PYTHONPATH
No description provided.