Skip to content

[UR][TEST] Clarify known-failure rationale for kernel subgroup query test#21566

Draft
kweronsx wants to merge 1 commit intosyclfrom
test/check-kernel-test-failing-adapters
Draft

[UR][TEST] Clarify known-failure rationale for kernel subgroup query test#21566
kweronsx wants to merge 1 commit intosyclfrom
test/check-kernel-test-failing-adapters

Conversation

@kweronsx
Copy link
Contributor

Modify UUR_KNOWN_FAILURE_ON macro invocation to see if the two adapters fail, since they do seem to have a non-trivial implementation, unlike the CUDA, HIP, NATIVE_CPU, and OFFLOAD adapters.

@kweronsx kweronsx force-pushed the test/check-kernel-test-failing-adapters branch 2 times, most recently from dda44b4 to 8f7dafc Compare March 23, 2026 10:32
@kweronsx kweronsx changed the title [UR][TEST] Check if level_zero and level_zero V2 adapters fail subgroup test [UR][TEST] Clarify known-failure rationale for kernel subgroup query test Mar 23, 2026
@kweronsx
Copy link
Contributor Author

kweronsx commented Mar 23, 2026

After reviewing the adapter implementations, it appears that many backend APIs do not provide the functionality needed to query the required number of work subgroups, instead returning a hardcoded value. Those that do support this query often fail because the hardware is incompatible with the kernel program built during the test, causing the test to fail before it can verify the retrieved data against the expected value.

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.

1 participant