sort ATen tests in CMake

[dagitses]

Stack from ghstack (oldest at bottom):

• register skipped ATen tests in CMake #84345
• -> sort ATen tests in CMake #84344
• build/test MaybeOwned_test in OSS and fix it #84342

Summary:
This will make it easier to compare and spot missing files.

Test Plan: Rely on CI.

Reviewers:

Subscribers:

Tasks:

Tags:

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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 our office hours

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

❌ 5 Failures

As of commit 21088c8:

The following jobs have failed:

• linux-bionic-py3.7-clang9 / test (crossref, 1, 2, linux.2xlarge)
• linux-bionic-py3.7-clang9 / test (default, 2, 2, linux.2xlarge)
• linux-bionic-py3.7-clang9 / test (dynamo, 2, 2, linux.2xlarge)
• linux-focal-py3.7-clang7-asan / test (default, 3, 5, linux.2xlarge)
• linux-focal-py3.7-gcc7 / test (default, 2, 2, linux.2xlarge)

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

[malfet]

LGTM, but can you please move this list to build_variables.bzl?

Also, why not use glob (perhaps as followup PR)

[dagitses]

LGTM, but can you please move this list to build_variables.bzl?

Also, why not use glob (perhaps as followup PR)

Sure. FWIW, we are using a glob internally.

[dagitses]

@pytorchbot merge --force='all breakages are from trunk, this is unlikely to add any breakages'

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered with the force (-f) flag. This means your change will be merged immediately, bypassing any CI checks (ETA: 1-5 minutes). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

[github-actions]

Hey @dagitses.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.