[SYCL][E2E] Don't link with L0 if not needed #20352
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
One of those tests constantly hangs and there is a chance that it happens because it directly links to the `l0_loader`. Considering that those tests don't use any L0 API, there is no need for them to be linked with L0.
AlexeySachkov
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
AlexeySachkov
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
AlexeySachkov
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
uditagarwal97
approved these changes
Oct 14, 2025
Contributor
Author
|
Some of pre-commit jobs were cancelled, but I don't think that they are crucial for this change and therefore I will proceed with merge |
AlexeySachkov
deleted the
private/asachkov/dont-link-with-l0-if-not-necessary
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One of those tests constantly hangs and there is a chance that it happens because it directly links to the
l0_loader. Considering that those tests don't use any L0 API, there is no need for them to be linked with L0.