Skip to content
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

Enable tests for v2 command buffer #2670

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Xewar313
Copy link
Contributor

@Xewar313 Xewar313 commented Feb 7, 2025

This PR enables conformance tests to work with v2 command buffer implementation. Unfortunately, some tests fail, due to the fact that respective functions are not implemented.

@Xewar313 Xewar313 requested a review from a team as a code owner February 7, 2025 09:48
@github-actions github-actions bot added conformance Conformance test suite issues. level-zero L0 adapter specific issues command-buffer Command Buffer feature addition/changes/specification labels Feb 7, 2025
Copy link
Contributor

@pbalcer pbalcer left a comment

Choose a reason for hiding this comment

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

We should keep UUR_KNOWN_FAILURE_ON on tests that we know are failing ;) That's what it's for.

EwanC added a commit to reble/llvm that referenced this pull request Feb 19, 2025
As discussed in oneapi-src/unified-runtime#2670 (comment) the `pCommandBufferDesc` parameter to `urCommandBufferCreateExp` is optional. However, the UR spec doesn't state what the configuration of the created command-buffer is when this isn't passed, and being optional is also inconsistent with the description parameters to urSamplerCreate & urMemImageCreate which are not optional. This PR updates the descriptor parameter to command-buffer creation to be mandatory to address these concerns.

Closes oneapi-src/unified-runtime#2673
EwanC added a commit to reble/llvm that referenced this pull request Feb 19, 2025
As discussed in oneapi-src/unified-runtime#2670 (comment) the `pCommandBufferDesc` parameter to `urCommandBufferCreateExp` is optional. However, the UR spec doesn't state what the configuration of the created command-buffer is when this isn't passed, and being optional is also inconsistent with the description parameters to urSamplerCreate & urMemImageCreate which are not optional. This PR updates the descriptor parameter to command-buffer creation to be mandatory to address these concerns.

Closes oneapi-src/unified-runtime#2673
steffenlarsen pushed a commit to intel/llvm that referenced this pull request Feb 20, 2025
As discussed in
oneapi-src/unified-runtime#2670 (comment)
the `pCommandBufferDesc` parameter to `urCommandBufferCreateExp` is
optional. However, the UR spec doesn't state what the configuration of
the created command-buffer is when this isn't passed, and being optional
is also inconsistent with the description parameters to urSamplerCreate
& urMemImageCreate which are not optional. This PR updates the
descriptor parameter to command-buffer creation to be mandatory to
address these concerns.

Closes oneapi-src/unified-runtime#2673

**Note**: This UR patch was previously approved and ready-to-merge in
oneapi-src/unified-runtime#2676 prior to the
repo move
@martygrant
Copy link
Contributor

Unified Runtime -> intel/llvm Repo Move Notice

Information

The source code of Unified Runtime has been moved to intel/llvm under the unified-runtime top-level directory,
all future development will now be carried out there. This was done in intel/llvm#17043.

The code will be mirrored to oneapi-src/unified-runtime and the specification will continue to be hosted at oneapi-src.github.io/unified-runtime.

The contribution guide has been updated with new instructions for contributing to Unified Runtime.

PR Migration

All open PRs including this one will be labelled auto-close and shall be automatically closed after 30 days.
To allow for some breathing space, this automation will not be enabled until next week (27/02/2025).

Should you wish to continue with your PR you will need to migrate it to intel/llvm.
We have provided a script to help automate this process.


This is an automated comment.

kbenzie pushed a commit to kbenzie/unified-runtime that referenced this pull request Feb 21, 2025
As discussed in
oneapi-src#2670 (comment)
the `pCommandBufferDesc` parameter to `urCommandBufferCreateExp` is
optional. However, the UR spec doesn't state what the configuration of
the created command-buffer is when this isn't passed, and being optional
is also inconsistent with the description parameters to urSamplerCreate
& urMemImageCreate which are not optional. This PR updates the
descriptor parameter to command-buffer creation to be mandatory to
address these concerns.

Closes oneapi-src#2673

**Note**: This UR patch was previously approved and ready-to-merge in
oneapi-src#2676 prior to the
repo move
@martygrant
Copy link
Contributor

Unified Runtime -> intel/llvm Repo Move Notice

Following on from the previous notice, we have now enabled workflows to automatically label and close PRs because the Unified Runtime source code has moved to intel/llvm.

This PR has now been marked with the auto-close label and will be automatically closed after 30 days.

Please review the previous notice for more information, including assistance with migrating your PR to intel/llvm.

Should there be a reason for this PR to remain open, manually remove the auto-close label.


This is an automated comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-close command-buffer Command Buffer feature addition/changes/specification conformance Conformance test suite issues. level-zero L0 adapter specific issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants