GPU CI Updates, main branch (2024.05.31.) #603
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
They now use the latest Acts Docker images, and set up their build environments in a slightly updated way.
krasznaa
force-pushed
the
CIUpdate-main-20240530
branch
from
ade7110 to
aeae7b8
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.
Switched the "GPU builds" to the latest Acts Docker images. At the same time I removed a CUDA build that I just didn't understand why we had. 😕 I just enabled
-DTRACCC_ENABLE_NVTX_PROFILING=TRUEfor our "standard" Release and Debug CUDA build instead.I instead added a oneAPI based build with an Intel backend. Since until now we've only been testing the build for NVIDIA and AMD backends in the CI for some reason. 😕 While the Intel backend allows us to do both Release and Debug builds, which should be good for the CI's test coverage. 🤔 (The NVIDIA and AMD backends still have issues with
assert(...)calls unfortunately. 😦 Making Debug builds impossible with them.)The big goal here is to finally revive #442, which should (hopefully...) start working with this new setup. 🤔