-
Notifications
You must be signed in to change notification settings - Fork 25.4k
[ONNX] Fix pow op export [1.5.1] #39791
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
[ONNX] Fix pow op export [1.5.1] #39791
Conversation
Summary: Fix pow type cast for opset 9 and update opset 12 Pull Request resolved: pytorch#38065 Differential Revision: D21485353 Pulled By: malfet fbshipit-source-id: 3993e835ffad07b2e6585eb5cf1cb7c8474de2ec
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 on green
💊 CI failures summary and remediationsAs of commit d6db5d5 (more details on the Dr. CI page):
🕵️ 1 new failure recognized by patternsThe following CI failures do not appear to be due to upstream breakages:
|
@houseroad looks like this is still failing, in spite of an onnx upgrade, is there any other things that may be holding us back? |
I tested locally test/onnx/test_pytorch_onnx_onnxruntime.py::TestONNXRuntime_opset11::test_topk_smallest_unsorted |
@KsenijaS - can you specify which PR/commit upgraded to the latest ORT version in the master CI today? This commit may be needed for 1.5.1 branch to make the test pass. |
PR: #36894 upgraded to the latest ORT version |
f7ec3e1
to
7bd10e2
Compare
Looks like even after the bump we're still failing the same test,
We're looking to close out the first RC for |
@seemethere I think this PR #37846 is missing, it updates failing test here: https://github.com/pytorch/pytorch/pull/37846/files#diff-92f53f0d2694170082f0ad81bfc05604R1486 |
@KsenijaS thanks for the link. I will cherry-pick just test fix and if it passes CI merge. |
7bd10e2
to
d6db5d5
Compare
Fix pow type cast for opset 9 and update opset 12
Also update ort-nighly as suggested in #39685 (comment)