This repository was archived by the owner on Mar 28, 2023. It is now read-only.
[SYCL] Change online compiler test to build IL based on queue #1028
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
Level-zero expects a single device when creating a module. This means that the online compiler test for level-zero has an assertion on the supplied context assuring only a single device. However, on multi-GPU systems this assertion will fail, in turn causing the test to report a failure. Rather than skipping the test on multi-GPU systems, these changes makes the test use the device in the queue rather than the first device in the associated context. Signed-off-by: Larsen, Steffen <[email protected]>
smaslov-intel
approved these changes
May 18, 2022
myler
pushed a commit
to myler/llvm-test-suite
that referenced
this pull request
Jun 17, 2022
…1028) Level-zero expects a single device when creating a module. This means that the online compiler test for level-zero has an assertion on the supplied context assuring only a single device. However, on multi-GPU systems this assertion will fail, in turn causing the test to report a failure. Rather than skipping the test on multi-GPU systems, these changes makes the test use the device in the queue rather than the first device in the associated context. Signed-off-by: Larsen, Steffen <[email protected]>
myler
added a commit
to myler/llvm-test-suite
that referenced
this pull request
Mar 22, 2023
Auto pulldown and update tc files for xmain branch on 20220720
aelovikov-intel
pushed a commit
to aelovikov-intel/llvm
that referenced
this pull request
Mar 27, 2023
…llvm-test-suite#1028) Level-zero expects a single device when creating a module. This means that the online compiler test for level-zero has an assertion on the supplied context assuring only a single device. However, on multi-GPU systems this assertion will fail, in turn causing the test to report a failure. Rather than skipping the test on multi-GPU systems, these changes makes the test use the device in the queue rather than the first device in the associated context. Signed-off-by: Larsen, Steffen <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Level-zero expects a single device when creating a module. This means that the online compiler test for level-zero has an assertion on the supplied context assuring only a single device. However, on multi-GPU systems this assertion will fail, in turn causing the test to report a failure. Rather than skipping the test on multi-GPU systems, these changes makes the test use the device in the queue rather than the first device in the associated context.