[ONNX] Add 0d-tensor test case in runtime check

[titaiwangms]

Stack from ghstack (oldest at bottom):

• -> [ONNX] Add 0d-tensor test case in runtime check #87212

[pytorch-bot]

🔗 Helpful Links

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

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

❌ 2 Failures

As of commit 80926c0:

The following jobs have failed:

• cuda11.6-py3.10-gcc7-sm86 / test (default, 1, 4, linux.g5.4xlarge.nvidia.gpu)
• macos-12-py3-arm64-mps / Run MPS tests

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

[BowenBao]

Why no_runtime, does ort fail?

[titaiwangms]

Why no_runtime, does ort fail?

Good point, and moved.

My execuse lol => In the original issue, that was an exporter issue, and didn't even hit ORT, and I thought 0d output might break verification (thank God it's not). Though I checked the prediction result, I didn't put it in runtime.

[titaiwangms]

@BowenBao PTAL

[titaiwangms]

@BowenBao PTAL. I moved the test to runtime.

[titaiwangms]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

Successfully rebased gh/AllenTiTaiWang/15/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/87212)

[titaiwangms]

@pytorchbot merge -g

[pytorchmergebot]

Merge started

Your change will be merged once all checks on your PR pass since you used the green (-g) flag (ETA: 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here