Skip to content

[UR][Test] Expose UR_CONFORMANCE_TARGET_TRIPLES to tests #18280

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

Maetveis
Copy link
Contributor

@Maetveis Maetveis commented May 1, 2025

Forward the value of UR_CONFORMANCE_TARGET_TRIPLES as an array to the conformance tests, and make it available to tests via KernelsEnvironment::HaveSourcesForTarget(target_name). This allows tests to require specific targets to be available.

@Maetveis Maetveis force-pushed the test-expose-ur-conformance-targets branch from 0f7fcdb to b36dce1 Compare May 1, 2025 08:46
@RossBrunton
Copy link
Contributor

What is the use case for this? Would a solution involving urDeviceSelectBinary not be better?

Forward the value of UR_CONFORMANCE_TARGET_TRIPLES as an array to the
conformance tests, and make it available to tests via
`KernelsEnvironment::HaveSourcesForTarget(target_name)`. This allows
tests to require specific targets to be available.
@Maetveis Maetveis force-pushed the test-expose-ur-conformance-targets branch from b36dce1 to 44bd62b Compare May 1, 2025 08:48
@@ -240,6 +241,14 @@ KernelsEnvironment::getKernelSourcePath(const std::string &kernel_name,
return path.str();
}

bool KernelsEnvironment::HaveSourcesForTarget(const std::string &target_name) {
auto it = std::find_if(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

std::any_of might be more idiomatic here.

@Maetveis Maetveis closed this May 8, 2025
@Maetveis Maetveis deleted the test-expose-ur-conformance-targets branch May 8, 2025 11:44
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.

2 participants