You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exception messages appear to be intended to be format strings but are not. This leads to variable specifiers in the raised error message.
File ~/.local/lib/python3.10/site-packages/torchao/quantization/utils.py:126, in guard_dtype_size(tensor_arg, arg_name, dtype, size)
124 def guard_dtype_size(tensor_arg, arg_name, dtype=None, size=None):
125 if dtype is not None and tensor_arg.dtype != dtype:
--> 126 raise ValueError("Expected Tensor argument {arg_name} to have dtype {dtype}, but got {tensor_arg.dtype} instead.")
127 if size is not None and tensor_arg.size() != size:
128 raise ValueError("Expected Tensor argument {arg_name} to have size {size}, but got {tensor_arg.size()} instead.")
ValueError: Expected Tensor argument {arg_name} to have dtype {dtype}, but got {tensor_arg.dtype} instead.
The text was updated successfully, but these errors were encountered:
* Add support for tiktoken and refactored runner structure
Summary:
Unified runner and move runner-et/CMakeLists.txt to runner/et.cmake and
runner-aoti/CMakeLists.txt to runner/aoti.cmake.
Added a root level CMakeLists.txt to build a tokenizer library and link
to both targets separately.
In CLI we need to specify the target to run:
```
cmake --build ./cmake-out --target et_run/aoti_run
```
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags:
* Fix CI
Summary:
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags:
* Fix more CI
Summary:
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags:
* Further fix CI
Summary:
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags:
* Lint`
Summary:
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags:
* Update build_android.sh
Summary:
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags:
* Rebase
Summary:
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags:
* Fix cmake commands in CI job
Summary:
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags:
Exception messages appear to be intended to be format strings but are not. This leads to variable specifiers in the raised error message.
The text was updated successfully, but these errors were encountered: