Skip to content

[SYCL][E2E] Accept default walk-order attribute in kernel_info_attr test#22279

Open
crystarm wants to merge 2 commits into
intel:syclfrom
crystarm:fix/sycl-kernel-info-attr
Open

[SYCL][E2E] Accept default walk-order attribute in kernel_info_attr test#22279
crystarm wants to merge 2 commits into
intel:syclfrom
crystarm:fix/sycl-kernel-info-attr

Conversation

@crystarm

Copy link
Copy Markdown
Contributor

Related to #22226.

What changed

Updated sycl/test-e2e/Basic/kernel_info_attr.cpp:

  • previously required info::kernel::attributes to be empty
  • now accepts either:
    • empty string, or
    • intel_reqd_workgroup_walk_order(0,1,2)

The test still verifies consistency between:

  • kernel::get_info<info::kernel::attributes>()
  • ext::oneapi::get_kernel_info<..., info::kernel::attributes>()

Why

On Level Zero, runtime/driver may expose default walk-order metadata as a kernel attribute.
This is valid behavior and should not fail the test.

Validation

  • Built and ran the updated test locally.
  • Legacy L0 path (UR_LOADER_USE_LEVEL_ZERO_V2=0) passes.
  • In current local environment, L0 V2 path throws UR_RESULT_ERROR_UNSUPPORTED_FEATURE before reaching the assertion.

@crystarm crystarm marked this pull request as ready for review June 10, 2026 15:04
@crystarm crystarm requested a review from a team as a code owner June 10, 2026 15:04
@crystarm crystarm requested a review from uditagarwal97 June 10, 2026 15:04
Comment on lines 4 to 5

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If this fix is intended to fix the test, you may also want to remove the UNSUPPORTED line, so we can test the fix in CI.

@crystarm crystarm force-pushed the fix/sycl-kernel-info-attr branch from 2a209f8 to 6cd9bc5 Compare June 10, 2026 15:18
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