[ET-VK][Ops] quantize ops skeleton test framework

[ahmtox]

Stack from ghstack (oldest at bottom):

• [ET-VK][Ops] dequantization op shaders and impl #11483
• [ET-VK][Ops] dequantize_per_token.default test setup #11482
• [ET-VK][Ops] dequantize_per_tensor.default test setup #11481
• [ET-VK][Ops] dequantize ops skeleton test framework #11480
• [ET-VK][Ops] quantization op shaders and impl #11369
• [ET-VK][Ops] quantize_per_tensor.default test setup #11368
• [ET-VK][Ops] quantize_per_token.default test setup #11367
• -> [ET-VK][Ops] quantize ops skeleton test framework #11366
• [ET-VK] double, short, and uint16 dtype runtime support #11365
• [ET] enabling half dtype input for quantization #11479

Skeleton framework that is needed to build out the quantize_per_tensor and quantize_per_token operators based on cpu implementation

Differential Revision: D75959066

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures

As of commit c043984 with merge base ef1d2ff ():

NEW FAILURES - The following jobs have failed:

• Lint / lintrunner / linux-job (gh)
  >>> Lint for backends/vulkan/test/op_tests/quantize_test.cpp:
• pull / unittest / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 58c440af2f0c9a335ca1662f77db9efde1e5a0146960f40181fe72ae8a35291d /exec failed with exit code 2
• pull / unittest-editable / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 80310ef5353db91211ec7e70d59e4d5540e6b5e44cda36b05ae121749f1e8947 /exec failed with exit code 2

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

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D75959066

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

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

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D75959066

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D75959066