[rocKE] Add the rocKE COD test driver - #2384
Draft
mhalk wants to merge 1 commit into
Draft
Conversation
Add run_rocke.sh, a standalone driver that runs one rocKE lane against the compiler-of-the-day and prints canonical ROCKE_RESULT rows plus a short summary, together with the modules it executes: the result line format, the comgr/toolchain probe, the COD interop smoke driver and the JUnit converter. Every row carries a relevance tier, so triage can tell a genuine compiler-of-the-day regression from a rocKE logic failure or this harness's own plumbing. rocke_relevance.py is a pytest plugin that records, per test, what evidence it saw; the JUnit converter joins that onto the rows, and the lanes without per-test evidence tag their rows from the lane's own class. A skip is scored on what is missing: this host (no GPU, no ROCm torch) keeps it green and unmeasured, while a reason naming the toolchain is a red row, since that is the compiler under test failing to do the work. The pytest lane provisions the test dependencies rocKE itself declares and builds its C++ engine extension with the COD through rocKE's own ROCKE_BUILD_PYBIND option, so the cross-engine tests run against a COD-built engine instead of skipping for a missing module. It lives here, beside the other run_*.sh drivers, so an engineer can check rocKE against a COD without the openmp-ci tree; the nightly drives the same script through its USER-run-rocKE-* wrappers, as CK's driver already does. AI-assisted.
mhalk
force-pushed
the
amd/dev/mhalkenh/feat/ci-run-rocke
branch
from
August 3, 2026 10:45
3d13fe2 to
1294ab8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add run_rocke.sh, a standalone driver that runs one rocKE lane against the compiler-of-the-day and prints canonical ROCKE_RESULT rows plus a short summary, together with the modules it executes: the result line format, the comgr/toolchain probe, the COD interop smoke driver and the JUnit converter.
Every row carries a relevance tier, so triage can tell a genuine compiler-of-the-day regression from a rocKE logic failure or this harness's own plumbing. rocke_relevance.py is a pytest plugin that records, per test, what evidence it saw; the JUnit converter joins that onto the rows, and the lanes without per-test evidence tag their rows from the lane's own class. A skip is scored on what is missing: this host (no GPU, no ROCm torch) keeps it green and unmeasured, while a reason naming the toolchain is a red row, since that is the compiler under test failing to do the work.
It lives here, beside the other run_.sh drivers, so an engineer can check rocKE against a COD without the openmp-ci tree; the nightly drives the same script through its USER-run-rocKE- wrappers, as CK's driver already does.
AI-assisted.
Motivation
Technical Details
Test Plan
Test Result
Submission Checklist