[DRAFT][rocgdb] Test filter standardization

[dileepr1]

Draft / WIP — opened to exercise CI against the paired TheRock branch. Do not merge as-is: THEROCK_COMMIT_REF in the workflows points at a feature branch and must be reverted to a pinned ROCm/TheRock SHA before merge.

Summary

Adopts TheRock's test-filter standardization (RFC0010) for ROCgdb, keeping all component-specific logic in this repo. TheRock stays component-agnostic — it only invokes its generic test_runner.py.

New sibling files under gdb/testsuite/ (installed verbatim by TheRock's existing testsuite install rule to tests/rocgdb/gdb/testsuite/):

• test_categories.yaml — source of truth for the quick/standard/comprehensive/full tiers (DejaGnu .exp selection, labels, timeouts).
• test_rocgdb.py — the DejaGnu launcher with a --tier flag (honours TEST_TYPE); self-locates rocgdb + testsuite from __file__ when run by ctest from the install tree.
• gen_ctestfile.py — dev tool that regenerates CTestTestfile.cmake from the YAML.
• CTestTestfile.cmake — pre-generated + committed; one add_test() per tier; each invokes test_rocgdb.py --tier <name> via a relative path (ctest sets the working directory to the test dir).

Workflows now invoke test_runner.py with TEST_COMPONENT=rocgdb / TEST_TYPE=standard instead of a per-component script.

Pairing

Paired with TheRock branch users/dravindr/tr_rocgdb, whose net footprint is just:

• fetch_test_configurations.py: rocgdb job → test_runner.py
• test_runner.py: a single COMPONENT_OVERRIDES["rocgdb"] entry → tests/rocgdb/gdb/testsuite

THEROCK_COMMIT_REF in therock-ci-linux.yml and therock-test-packages.yml is temporarily set to users/dravindr/tr_rocgdb so this draft builds/tests against that paired state.

Flow

workflow → test_runner.py (TheRock, generic)
        → ctest -L <tier> --test-dir tests/rocgdb/gdb/testsuite
            → CTestTestfile.cmake (ROCgdb-owned)
                → ./test_rocgdb.py --tier <name> (ROCgdb-owned)
                    → reads ./test_categories.yaml → make check TESTS=...

Test plan

• TheRock CI Linux build (gfx94X-dcgpu) succeeds against tr_rocgdb
• Run Tests job exercises ctest -L standard → test_rocgdb.py --tier standard (GCC + LLVM matrix)
• Revert THEROCK_COMMIT_REF to a pinned ROCm/TheRock SHA before un-drafting

🤖 Generated with Cursor

Made with Cursor

[lumachad]

Thanks for the PR. Some preliminary comments. I think it's mostly OK, pending adjusting location of files, lists of tests and validation.

[lumachad]

Thanks for the updates. Let me go through this again.

[lumachad]

Let's wait until #117 gets merged, as that one has a large change to test_rocgdb.py. Since this one touches that same script, we should avoid needless conflict resolution cycles.

[lumachad]

#117 has been merged. I think we can rebase the changes in this PR on top of current test_rocgdb.py.

[lumachad]

@dileepr1 Thanks. Let me go through this again and see what we should put into the test categories.

[lumachad]

@dileepr1 With rocgdb testing we have both CPU and GPU tests that must be routed to the appropriate runners to make the best use of resources. Can these filters handle that?