[WIP] Add test_torchinductor_opinfo.py to triton-cpu tests

[davidberard98]

Stack from ghstack (oldest at bottom):

• -> [WIP] Add test_torchinductor_opinfo.py to triton-cpu tests #145865

I'm guessing this isn't going to pass, but I want to see how long the CI takes.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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.

❌ 2 New Failures, 1 Unrelated Failure

As of commit f768b96 with merge base a08f7f3 ():

NEW FAILURES - The following jobs have failed:

• Check Labels / Check labels (gh)
  RuntimeError: Error checking labels: PR does not have required labels
• inductor / unit-test / linux-jammy-cpu-py3.12-gcc11-inductor-triton-cpu / test (inductor-triton-cpu, 1, 1, linux.12xlarge) (gh)
  'Test'

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• inductor / linux-jammy-cpu-py3.9-gcc11-inductor / test (inductor_torchbench_cpu_smoketest_perf, 1, 1, linux.24xl.spr-metal) (gh) (trunk failure)
  Process completed with exit code 1.

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

[github-actions]

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[davidberard98]

cc @kundaMwiza it looks like we do have triton-cpu tests running, but the opinfo tests aren't running.

If you're interested (and if the CI doesn't take too long - which is what I'm testing in this PR) - we could probably enable these tests. But I'm guessing we'd have to do a first pass to mark all the failing tests as skipped, so that the CI isn't red.

cc @minjang @int3

[davidberard98]

... actually, I realize we probably also need to set torch._inductor.config.cpu_backend = "triton" to get these to run correctly.

[kundaMwiza]

@davidberard98 Thanks. I did try running the tests locally and there were quite a lot of failures, some can be xfailed, but others result in a process crash. I ran the tests serially on a single node and it took 4 hours, but best to run it in pytorch CI to get a better view.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.