Fix ONNX operator_export_type on the new registry #87735 #90044
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A cherry-pick for the 1.13.1 release.
Original PR: #87735
Below is the description of the original PR.
Fixes #87313
Pytorch's ONNX pipelines do not run with
BUILD_CAFFE2=0
, so tests foroperator_export_type==ONNX_ATEN
orONNX_ATEN_FALLBACK
are not fully tested, which caused this regression to the core feature of ONNX exporter: ONNX ATen fallback.This PR fixes this regression, but we discuss with Meta on how to use only
BUILD_CAFFE2=0
builds instead of ``BUILD_CAFFE2=1`