Per RFC0010,
rocprofiler-compute is tested through the unified test_runner.py, not a
dedicated per-component script.
Components may run their own CI with different exclusion needs, so a single
generic <category>_exclude is not the right lever for deciding what TheRock CI
should skip. That is why ROCm/rocm-systems#7658 adds category-wise
<category>_therock_ci_exclude labels for rocprofiler-compute in
tests/test_categories.yaml — TheRock-CI-specific excludes.
test_runner.py should consume those labels so TheRock CI excludes the right
tests, run rocprofiler-compute's ctest serially (its pytest tests parallelize
internally), and the redundant test_rocprofiler_compute.py should be removed.
Per RFC0010,
rocprofiler-compute is tested through the unified
test_runner.py, not adedicated per-component script.
Components may run their own CI with different exclusion needs, so a single
generic
<category>_excludeis not the right lever for deciding what TheRock CIshould skip. That is why ROCm/rocm-systems#7658 adds category-wise
<category>_therock_ci_excludelabels for rocprofiler-compute intests/test_categories.yaml— TheRock-CI-specific excludes.test_runner.pyshould consume those labels so TheRock CI excludes the righttests, run rocprofiler-compute's ctest serially (its pytest tests parallelize
internally), and the redundant
test_rocprofiler_compute.pyshould be removed.