Add InstanceNorm3d alias-conversion regression coverage - #2820
Open
sfeng01-tech wants to merge 1 commit into
Open
Add InstanceNorm3d alias-conversion regression coverage#2820sfeng01-tech wants to merge 1 commit into
sfeng01-tech wants to merge 1 commit into
Conversation
sfeng01-tech
marked this pull request as ready for review
August 17, 2026 21:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
#2666 reported that converting
InstanceNorm3d(track_running_stats=True)through
torch.exportfailed with:The
aliasoperator is already registered on currentmain, so the reportedfrontend conversion failure is fixed. This PR adds regression coverage for that
path.
Changes
InstanceNorm3d.track_running_stats=FalseandTrue.torch.exportfrontends.milinternal, ensuring the test covers frontend conversion withoutrequiring Core ML runtime execution.
Why conversion-only?
Core ML runtime
instance_normsupports rank-3 and rank-4 tensors only.InstanceNorm3duses a rank-5 tensor, so runtime prediction is unsupportedindependently of the
aliasconversion issue.Verification
Fixes #2666.