Enable CI tests for CPU-based SYCL builds #636
Merged
Conversation
This file contains 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
stephenswat
added
cicd
As it stands, we only test our SYCL code on the CI bridge, and that only runs on GPU-like platforms. While it is good that we test there, it is also important for us to test this code on CPU platforms. Indeed, such platforms behave differently in terms of lockstep execution and memory allocation.
stephenswat
force-pushed
the
ci/sycl_cpu_tests
branch
from
3dfdd8f to
f2c98c2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As it stands, we only test our SYCL code on the CI bridge, and that only runs on GPU-like platforms. While it is good that we test there, it is also important for us to test this code on CPU platforms. Indeed, such platforms behave differently in terms of lockstep execution and memory allocation.