[ONNX] Export quantized::layer_norm to LayerNormalization in opset >=17

[NathanielB123]

Fixes #126160

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/126555

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Upgrade MacOS runner to 14

❌ 1 New Failure, 10 Unrelated Failures

As of commit c5b5b5e with merge base 31ea829 ():

NEW FAILURE - The following job has failed:

• pull / linux-focal-cuda12.4-py3.10-gcc9 / build (gh)
  /var/lib/jenkins/workspace/aten/src/ATen/cuda/CUDASparseDescriptors.h:119:68: error: ‘cusparseStatus_t cusparseCreateBsrsm2Info(bsrsm2Info**)’ is deprecated: The routine will be removed in the next major release [-Werror=deprecated-declarations]

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / linux-focal-cuda12.1-py3.10-gcc9 / test (default, 2, 5, linux.4xlarge.nvidia.gpu) (gh) (similar failure)
  test_public_bindings.py::TestPublicBindings::test_correct_module_names
• pull / linux-focal-cuda12.1-py3.10-gcc9-sm86 / test (default, 2, 5, linux.g5.4xlarge.nvidia.gpu) (gh) (similar failure)
  test_public_bindings.py::TestPublicBindings::test_correct_module_names
• pull / linux-focal-py3.11-clang10 / test (crossref, 2, 2, linux.2xlarge) (gh) (similar failure)
  test_public_bindings.py::TestPublicBindings::test_correct_module_names
• pull / linux-focal-py3.11-clang10 / test (default, 2, 3, linux.2xlarge) (gh) (similar failure)
  test_public_bindings.py::TestPublicBindings::test_correct_module_names
• pull / linux-focal-py3.12-clang10 / test (default, 2, 3, linux.2xlarge) (gh) (similar failure)
  test_public_bindings.py::TestPublicBindings::test_correct_module_names
• pull / linux-focal-py3.8-clang10 / test (crossref, 2, 2, linux.2xlarge) (gh) (similar failure)
  test_public_bindings.py::TestPublicBindings::test_correct_module_names
• pull / linux-focal-py3.8-clang10 / test (default, 2, 3, linux.2xlarge) (gh) (similar failure)
  test_public_bindings.py::TestPublicBindings::test_correct_module_names
• pull / linux-jammy-py3.10-clang15-asan / test (default, 2, 6, linux.4xlarge) (gh) (similar failure)
  test_public_bindings.py::TestPublicBindings::test_correct_module_names
• pull / linux-jammy-py3.8-gcc11 / test (default, 2, 3, linux.2xlarge) (gh) (similar failure)
  test_public_bindings.py::TestPublicBindings::test_correct_module_names

UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:

• pull / linux-focal-cuda12.4-py3.10-gcc9-sm86 / build (gh) (#127104)
  /var/lib/jenkins/workspace/aten/src/ATen/cuda/CUDASparseDescriptors.h:119:68: error: ‘cusparseStatus_t cusparseCreateBsrsm2Info(bsrsm2Info**)’ is deprecated: The routine will be removed in the next major release [-Werror=deprecated-declarations]

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[linux-foundation-easycla]

• ❌ - login: @NathanielB123 / name: Nathaniel Burke . The commit (8de6e54, c5b5b5e) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[titaiwangms]

Hi @NathanielB123 Please sign CLA as it suggests.

[NathanielB123]

Hi @NathanielB123 Please sign CLA as it suggests.

I think I count as corporate contributor given I am interning at Arm working on ML stuff right now. I sent the email to the CLA manager so I guess I just have to wait now (will also ask on Monday to double check how this stuff works).

[titaiwangms]

Hi @NathanielB123 Please sign CLA as it suggests.

I think I count as corporate contributor given I am interning at Arm working on ML stuff right now. I sent the email to the CLA manager so I guess I just have to wait now (will also ask on Monday to double check how this stuff works).

I remember it's easier to sign as individual contributor.

This PR was reopened (likely due to being reverted), so your approval was removed. Please request another review.

[NathanielB123]

Oops sorry I forgot about this. I asked around a bit at work and it sounds like the process for getting open-source contributions approved is stupidly complicated and the standard approach in my team is to sidestep this by only opening GH issues, not PRs. Very dumb but ¯\_(ツ)_/¯, closing.

If someone was to create their own PR fixing the same root issue in perhaps a vaguely similar way (because the fix really is quite obvious) I assume there would be no problems, but IANAL.

[titaiwangms]

Oops sorry I forgot about this. I asked around a bit at work and it sounds like the process for getting open-source contributions approved is stupidly complicated and the standard approach in my team is to sidestep this by only opening GH issues, not PRs. Very dumb but ¯_(ツ)_/¯, closing.

If someone was to create their own PR fixing the same root issue in perhaps a vaguely similar way (because the fix really is quite obvious) I assume there would be no problems, but IANAL.

Thanks for trying! I will open another PR for this.