-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Work-Around: NVCC 11.4.0 - 11.8.0 #4220
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
Conversation
Adds a targeted NVCC work around for limited number of CUDA releases. Fixed in NVCC development.
Could we also bump the docker image used to build the cuda tests? |
Good point. Bumped. |
Thanks! I'd like to target a 2.10.1 release in the next (max) 2.5 weeks, hopefully sooner. (That's before 3.11, if you are curious to the selection of the max date ;) ). |
I think this PR is giving me trouble when updating the smart_holder branch (#4227). See below. @ax3l did you try to add https://github.com/pybind/pybind11/actions/runs/3207229735/jobs/5241897361
|
I made a simple reproducer for master: PR #4228 Evidently this workaround only trades one error for another. I recommend rolling back this PR as soon as possible. (I'll do that on the smart_holder branch now, to unblock the update.) My test is pretty small but can probably be reduced further. |
This reverts commit e21cdc3.
…ment)." This reverts commit d7e65a3.
Continued in #4228 |
Missed by a week, but it's out now. |
Adds a targeted NVCC work around for limited number of CUDA releases. Fixed in NVCC development.
Fix #4193
Description
Suggested changelog entry: