-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add nvhpc devcontainer to CI #1488
base: main
Are you sure you want to change the base?
Conversation
@@ -84,6 +87,7 @@ pull_request: | |||
- {cuda: *cuda_curr, os: 'windows2022', cpu: 'amd64', compiler: *msvc2019, std: [14, 17], jobs: ['build']} | |||
- {cuda: *cuda_curr, os: 'windows2022', cpu: 'amd64', compiler: *msvc2022, std: [14, 17, 20], jobs: ['build']} | |||
- {cuda: *cuda_curr, os: 'ubuntu22.04', cpu: 'amd64', compiler: *oneapi, std: [11, 14, 17], jobs: ['build']} | |||
- {cuda: *cuda_curr, os: 'ubuntu22.04', cpu: 'amd64', compiler: *nvhpc, std: [11, 14, 17, 20], jobs: ['build']} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note for the future: This is a little wonky because it would lead someone to believe that they could control the CUDA version separate from the nvhpc version. The current matrix logic isn't built to expect that a host compiler would come with its own CTK. Not sure how to cleanly handle that, but that'll be a problem for future self :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is but I would rather not completely rewrite the whole matrix for that one use case
Co-authored-by: Jake Hemstad <jhemstad@nvidia.com>
We also support the latest nvc++ as a host compiler, so we should test it in CI