Skip to content

Conversation

@rocm-devops
Copy link
Contributor

This PR recreates Gerrit's patch: https://gerrit-git.amd.com/c/compute/ec/hip-tests/+/1193797

Pending conversation from that patch:

Maneesh Gupta
I guess another way to implement this test would be to have the REQUIRE line only in the nv case, while in the amd case we would do the set, but not the REQUIRE.

Gerardo Hernandez
If we do the setAttribute(), but not the REQUIRE() on AMD, as you say, it would not demonstrate that the value being passed to hipFuncSetAttribute() is ignored on AMD. i.e. in the test I am demonstrating that the value stays the same; hence proving it is ignored.
Is that not the right thing to do?

@mangupta_amdeng

- Remove Unit_hipFuncSetAttribute_Positive_PreferredSharedMemoryCarveout_Not_Supported and change Unit_hipFuncSetAttribute_Positive_PreferredSharedMemoryCarveout so it expects the value to be ignored if withing the allowed range

Change-Id: I6f52788667082075dd46605dfa84d460c3acac0d
@rocm-devops
Copy link
Contributor Author

Imported to ROCm/rocm-systems

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants