-
Notifications
You must be signed in to change notification settings - Fork 7.1k
Update hardcoded WIN-CUDA from 11.1 with 11.3 #5451
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
💊 CI failures summary and remediationsAs of commit 860566b (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
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.
LGTM, thanks @malfet. Let's merge after the CI passes.
@malfet The failing test is due to an issue on a dependency: pyreadline/pyreadline#65 @pmeier Any thoughts on how we could get around it until this is patched upstream? |
[Edit] Ok, for some reason |
This seems to be a problem with |
|
I'm not sure how this relates to the question. To elaborate, I was asking why we are using the I personally never had issues with stuff from |
@malfet What is the recommended way to move forward? As you know the release is near and we need to fix CI jobs to avoid a bodged release. I'm also concerned that the job unittest_windows_gpu_py3.8 is failing with memory access issues on this branch. Given it doesn't fail on other branches I believe it's due to the switch of cuda versions. The constraint added above didn't seem to work and the unittest_windows_cpu_py3.10 still fails. If we can't use |
Also, remove reference to conda-forge, all CUDA toolchain should be available from NVIDIA channel
e23189d
to
46f1697
Compare
Ok, looks like gaussian blur fails with kernel sizes of 23x23, which sounds suspiciously familiar
@IvanYashchuk, does it sounds familiar? |
No, I don't know the source of the problem. |
b0890f5
to
737af02
Compare
737af02
to
860566b
Compare
Also, remove reference to conda-forge, all CUDA toolchain should be available from NVIDIA channel Install h5py from pip on Windows and skip failing gaussian_blur tests if Win+CUDA11.3 is used
Also, remove reference to conda-forge, all CUDA toolchain should be available from NVIDIA channel Install h5py from pip on Windows and skip failing gaussian_blur tests if Win+CUDA11.3 is used Co-authored-by: Nikita Shulga <[email protected]>
Summary: Also, remove reference to conda-forge, all CUDA toolchain should be available from NVIDIA channel Install h5py from pip on Windows and skip failing gaussian_blur tests if Win+CUDA11.3 is used Reviewed By: jdsgomes Differential Revision: D34475316 fbshipit-source-id: 463ef028d315942efae956e8a5b314f8868a2975
Also, remove reference to conda-forge, all CUDA toolchain should be
available from NVIDIA channel
Install h5py from pip on Windows and skip failing gaussian_blur tests if Win+CUDA11.3 is used