Skip to content

fix(hipdnn): move SdpaFwd test bundles into the post-rename directory - #11481

Open
zhihuidu-amd wants to merge 1 commit into
ROCm:developfrom
zhihuidu-amd:users/zhihuidu-amd/fix-bundle-dir
Open

fix(hipdnn): move SdpaFwd test bundles into the post-rename directory#11481
zhihuidu-amd wants to merge 1 commit into
ROCm:developfrom
zhihuidu-amd:users/zhihuidu-amd/fix-bundle-dir

Conversation

@zhihuidu-amd

Copy link
Copy Markdown
Contributor

PR #10162 renamed dnn-providers/integration-tests/integration_test_bundles to integration-test-bundles. PR #9589 was in flight across that rename and recreated the old path, so its three Flash2 golden-reference bundles (hd128_causal_gqa4, hd128_causal_mha, hd64_causal) landed in a directory nothing reads. They were the only content left there.

Reported by @ScottTodd on #9589: the new directory carries a *.bin catch-all in .gitignore so DVC-pulled tensors can never be staged by accident, while the old path has no such rule -- so after dvc pull the twelve .bin files show up as untracked for everyone.

There is a second consequence that was not reported, and it is the more significant one: the bundles were never loaded by any test. dnn-providers/integration-tests/CMakeLists.txt:133 copies only integration-test-bundles/ into the build tree and installs only that at :149, and both BundleRegistration.hpp:214 and main.cpp:134 resolve /../lib/integration-test-bundles. Nothing in the tree references the underscore path. So these three bundles have been inert since the rename.

Pure git mv of nine files: 9 renames, 0 insertions, 0 deletions. No code change is needed -- the harness discovers bundles by scanning the directory, not from a manifest, and none of the three names already existed under the new path so there is no collision.

DVC is unaffected. Each .tensors.dvc entry addresses its blob by md5 content hash with path holding only the bare filename relative to the pointer, so moving the pointer does not change what dvc pull fetches. Verified the pointer contents are byte-identical after the move, and that git check-ignore now matches the .bin files against integration-test-bundles/.gitignore:4.

Motivation

Technical Details

Test Plan

Test Result

Submission Checklist

PR ROCm#10162 renamed dnn-providers/integration-tests/integration_test_bundles to
integration-test-bundles. PR ROCm#9589 was in flight across that rename and
recreated the old path, so its three Flash2 golden-reference bundles
(hd128_causal_gqa4, hd128_causal_mha, hd64_causal) landed in a directory
nothing reads. They were the only content left there.

Reported by @ScottTodd on ROCm#9589: the new directory carries a `*.bin` catch-all
in .gitignore so DVC-pulled tensors can never be staged by accident, while the
old path has no such rule -- so after `dvc pull` the twelve .bin files show up
as untracked for everyone.

There is a second consequence that was not reported, and it is the more
significant one: **the bundles were never loaded by any test.**
dnn-providers/integration-tests/CMakeLists.txt:133 copies only
integration-test-bundles/ into the build tree and installs only that at :149,
and both BundleRegistration.hpp:214 and main.cpp:134 resolve
<exe>/../lib/integration-test-bundles. Nothing in the tree references the
underscore path. So these three bundles have been inert since the rename.

Pure `git mv` of nine files: 9 renames, 0 insertions, 0 deletions. No code
change is needed -- the harness discovers bundles by scanning the directory,
not from a manifest, and none of the three names already existed under the new
path so there is no collision.

DVC is unaffected. Each .tensors.dvc entry addresses its blob by md5 content
hash with `path` holding only the bare filename relative to the pointer, so
moving the pointer does not change what `dvc pull` fetches. Verified the
pointer contents are byte-identical after the move, and that
`git check-ignore` now matches the .bin files against
integration-test-bundles/.gitignore:4.
@therock-pr-bot

therock-pr-bot Bot commented Aug 31, 2026

Copy link
Copy Markdown

✅ All Checks Passed — Ready for Review

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

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

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

🙋 Wish to Override Policy?

@therock-pr-bot

Copy link
Copy Markdown

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant