[Test] Add vllm_ut test

[pranavprakash-amd]

Motivation

Adding test to validate vllm specific scenarios

Technical Details

Test Plan

Test Result

Submission Checklist

• Look over the contributing guidelines at https://github.com/ROCm/ROCm/blob/develop/CONTRIBUTING.md#pull-requests.

[y1k2chaitanya]

Automated review — 1 blocker (required CI check failing):

• pre-commit (black --check) is FAILING → black would reformat both new files, so this required gate is red and blocks merge. Run black tests/frameworks/vllm/ and push. Specifics:
  • tests/frameworks/vllm/conftest.py:96 — needs a blank line after import logging, the any(...) generator collapsed to one line (~L102), and the final pytest.skip(...) collapsed (~L115).
  • tests/frameworks/vllm/test_vllm_ut.py:167 — collapse the split apt-get ... "curl libsodium23" string, and reformat the three commands.extend([...]) blocks (~L177-L208) and the tests-tree commands.extend([...]) (~L214) to black's style.

Non-blocking nits (no action required to approve): module docstrings reference the path tests/e2e/frameworks/vllm/ but the files live at tests/frameworks/vllm/.

All imports (framework.reporting.allure_reporter.report_metric), the container_executor fixture, probe()/run(), and the --no-gpu/--container-image options resolve, and the dotted markers match the registered taxonomy — so once black passes this is otherwise mergeable.

[mparamas-amd]

vllm tests placeholder may be ./tests/e2e//test_vllm_ut.py

[mparamas-amd]

update per directory category profiles in frameworks/markers/taxonomy.py

[pranavprakash-amd]

Run result::

====================================================== ROCm Test Suite Summary ======================================================
Test Directory PASS FAIL SKIP ERROR Duration
─────────────────────────────────────────────────────────────
tests/frameworks/vllm 0 8 0 0 1726.2 s
─────────────────────────────────────────────────────────────
TOTAL 8 tests │ 0 passed │ 8 failed │ 0 skipped │ 0 error │ 1726.2 s

Failed tests:
• tests/frameworks/vllm/test_vllm_ut.py::test_vllm_ut[core]
• tests/frameworks/vllm/test_vllm_ut.py::test_vllm_ut[test_regression_py]
• tests/frameworks/vllm/test_vllm_ut.py::test_vllm_ut[engine_test_sequence_py_test_config_py_test_logger_py]
• tests/frameworks/vllm/test_vllm_ut.py::test_vllm_ut[tokenization]
• tests/frameworks/vllm/test_vllm_ut.py::test_vllm_ut[test_logits_processor_py]
• tests/frameworks/vllm/test_vllm_ut.py::test_vllm_ut[tool_use]
• tests/frameworks/vllm/test_vllm_ut.py::test_vllm_ut[kernels_quantization_test_awq_triton_py]
• tests/frameworks/vllm/test_vllm_ut.py::test_vllm_ut_int4_awq_triton

Note: The failures are part of the pytest tests that are triggered inside the vllm. Those failures are not because of the current test as its just invoking them inside the container.