Disable nnc/test_aot_compile.sh

[ZolotukhinM]

Stack from ghstack (oldest at bottom):

• -> Disable nnc/test_aot_compile.sh #81196

Deprecation: NNC backend for mobile is not being worked upon actively. It is slated to be deprecated.

@bypass-github-export-checks

Differential Revision: D37746019

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/81196
• 📄  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
• ↩️  [fb-only] Re-run with SSH instructions

✅ 1 Base Failures

As of commit 8d8a539 (more details on the Dr. CI page):

Expand to see more

---

✅ None of the CI failures appear to be your fault 💚

---

• 1/1 broken upstream at merge base 4503c45 since Jul 10

---

🚧 1 ongoing upstream failure:

These were probably caused by upstream breakages that are not fixed yet.

• pull / linux-focal-py3.7-gcc7 / test (backwards_compat, 1, 1, linux.2xlarge) since Jul 10 (4503c45)
  • 🔁 rerun

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[ZolotukhinM]

@ZolotukhinM has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[mruberry]

Stamped!

[ZolotukhinM]

@ZolotukhinM has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[ZolotukhinM]

@ZolotukhinM has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[facebook-github-bot]

@pytorchbot merge -f

(Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally)

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here

[github-actions]

Hey @ZolotukhinM.
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.