[TheRock] CDash Reporting for rocprofiler-sdk tests

[EvanPhoukong]

Motivation

Report rocprofiler-sdk configure, build, and test results from TheRock CI to CDash while preserving the existing local test flow.

JIRA Ticket

AIPROFSDK-34

Technical Details

• Adds an optional --enable-cdash execution path and enables it for rocprofiler-sdk CI.
• Generates a CTest dashboard using the same configure, build, and test commands as the direct runner.
• Includes PR, platform, GPU, build variant, artifact run, and test run information in CDash submissions.
• Preserves ASan exclusions and supports optional strict submission.
• Keeps direct CMake and CTest execution as the default for local use.

Test Plan

• Run the dashboard unit tests.
• Confirm CI submits configure, build, and test results with the expected metadata.
• Confirm local execution still uses the direct runner.

Test Result

• rocprofiler_sdk_dashboard_test.py: 8 passed.
• Confirmed PR submission is correct in the Dashboard

Submission Checklist

• Look over the contributing guidelines.

[marbre]

As you touched modules it will trigger a review request anyway. Please mark this as minimum a draft. However, you probably don't need a PR at all and you can rather trigger a specific action you want to run instead.

[therock-pr-bot]

❌ PR Check — Action Required

Check	Status	Details
🌿 Branch Name	✅ Pass	—
📝 PR Title/Description	❌ Fail	Error: PR description must reference a JIRA ID, ISSUE ID, or a GitHub closing keyword. Expected: include a JIRA ID / ISSUE ID line (separator : or -, or omitted; value may be a JIRA key, a number with/without #, or a link), OR a closing keyword + issue reference. Accepted examples: • JIRA ID : TESTAUTO-6039 • JIRA ID - #330 • JIRA ID #330 • JIRA ID (on separate line) ROCM-25757 • ISSUE ID : TESTUTO-3334 • ISSUE ID #3334 • ISSUE ID - TESTAUTO-3433 • ISSUE ID (on separate line) AIRUNTIME-2352 • ISSUE ID : https://github.com/<org_name>/<repo_name>/issues/1234 • Closes #10 • Fixes octo-org/octo-repo#100 • Resolves: #123 • #123 • https://github.com/<org_name>/<repo_name>/issues/123 Current: no valid JIRA/ISSUE/closing-keyword reference found
⛔ Forbidden Files	✅ Pass	—
🧪 Unit Test	✅ Pass	—
🔎 pre-commit	⏳ Pending	⏳ Still running…
🚫 Draft PR	🔜 To Be Enabled	—
🚩 Feature Flag	🔜 To Be Enabled	—
📊 Code Coverage	🔜 To Be Enabled	—

⚠️ 1 policy check(s) failed. Please address the issues above before this PR can be Reviewed.

🚫 Please fix the failed policies

• ❌ PR Title/Description

The Not ready to Review label was added to this PR. Once all policies pass, the label is removed automatically.

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

[therock-pr-bot]

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

• ❌ PR Title/Description

The Not ready to Review label has been added to this PR.
Once all policies pass, the label will be removed automatically.