Make the CI actually use some GPUs #58
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
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.
The CI now uses some actual GPUs for testing; for now an NVIDIA dGPU and an Intel iGPU. (i.e. AMD still stays untested here for now—though it should be really similar to the NVIDIA code paths most of the time)
Thus, also switch the CI tests from
doubletolong; since the currently-used iGPU doesn't support any double it seems.Currently, we test CUDA, ACPP (both for NVIDIA), and oneAPI (for Intel).
Downside is that it's right now all a self-hosted (i.e. more unstable) runner. I.e. if we take it down or re-setup it, all logs associated with it will be lost.
Also fix a bug in the SYCL reductions (which only became apparent by the CI).