-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Output mismatch of duplicate torch.Tensor.to nodes after optimization #18211
Comments
This issue has been automatically marked as stale due to inactivity and will be closed in 7 days if no further activity occurs. If further support is needed, please provide an update and/or more details. |
@Azyka this might be fixed after pytorch/pytorch#96320 if you set Try it out and let us know how it goes |
@thiagocrepaldi I tried the
|
This issue has been automatically marked as stale due to inactivity and will be closed in 30 days if no further activity occurs. If further support is needed, please provide an update and/or more details. |
Describe the issue
ONNX opset version: 14
When 2 duplicate nodes(which have the same inputs and outputs) of torch.Tensor.to are defined, the model produce wrong results after ort optimization.
To reproduce
Model code:
Output:
Model0 produces array(True) after optimization, which is supposed to be array(False).
Urgency
This is an incorrect functionality implementation. It may cause severe bugs for those systems on the top of ORT.
Platform
Linux
OS Version
Ubuntu 22.04.3 LTS (x86_64)
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
1.15.1
ONNX Runtime API
Python
Architecture
X64
Execution Provider
Default CPU
Execution Provider Library Version
No response
The text was updated successfully, but these errors were encountered: