[avansick-amd]

Co-authored-by: Claude Opus 5 noreply@anthropic.com
Signed-off-by: Adam Van Sickle adam.vansickle@amd.com

Motivation

rocprofiler-compute gained a THEROCK_BUNDLED_ZLIB runtime dep in #7421, but the
committed consumer graph was never regenerated. The drift check compares the whole
file, so any PR touching a graph-affecting path either fails it or has to carry this
line in an unrelated diff. Same class as #7298 / #7297.

Technical Details

Regenerated test_tools/therock_consumer_graph.json with
check_consumer_graph_drift.py --write from a full-tree THEROCK_ENABLE_ALL=ON
gfx94X-dcgpu configure. No other files change.

The diff is one line: rocprofiler-compute added to therock-zlib's consumers.

rocprofiler-compute has a key in fetch_test_configurations.py,
so changes to therock-zlib can now schedule its tests.
That follows from the dependency #7421 added.

Test Plan

• Regenerated locally, then confirmed the result matches what CI independently
  computed on [profiler] Add profiler-hub as a TheRock subproject and artifact #7376.

Test Result

• Consumer graph drift check: pass.

Submission Checklist

• Look over the contributing guidelines at https://github.com/ROCm/TheRock/blob/main/CONTRIBUTING.md.

[therock-pr-bot]

✅ All Policy Checks Passed

Check	Status	Details
📝 PR Description	✅ Pass	—
⛔ Forbidden Files	✅ Pass	—
🧪 Unit Test	✅ Pass	PR does not contain code files — Unit Test auto-passed
🚫 Draft PR	🔜 To Be Enabled	—
🚩 Feature Flag	🔜 To Be Enabled	—
📊 Code Coverage	🔜 To Be Enabled	—

🎉 All policy checks passed!

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

🙋 Wish to Override Policy?

[therock-pr-bot]

🎉 All checks passed! This PR is ready for review.

[ScottTodd]

That's a very long AI generated PR description for what could be summarized in one sentence as:

Commit <> did not update test_tools/therock_consumer_graph.json, this fixes it.

The one additional detail that is useful in the current description is the lack of a push trigger in the workflow for post-merge coverage that would make this easier to track through the history. We will not "regenerate the committed graph after a merge" automatically though, as that would require granting automation commit access.

Please read https://github.com/ROCm/TheRock/blob/main/CONTRIBUTING.md#ai-tool-use-policy for future PRs.

[ScottTodd]

For reference, here's another PR updating the committed graph: #7297. Still verbose, but about half as much text.

[avansick-amd]

For reference, here's another PR updating the committed graph: #7297. Still verbose, but about half as much text.

Thanks! I was just looking through that one actually. I was about to update with a new description more or less lifted from it.

[ScottTodd]

Passing here: https://github.com/ROCm/TheRock/actions/runs/32096784259/job/95589599898, lgtm.

I think we should also add a push trigger to https://github.com/ROCm/TheRock/blob/main/.github/workflows/test_consumer_graph_drift.yml to make it easier to spot when it started failing (it takes ~10 minutes to run on github-hosted runners so running on only pushes affecting the relevant files is a nice optimization instead of running on push for all file changes)