-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update feedstock to use cirun-openstack-cpu-large with Cirun #21
Update feedstock to use cirun-openstack-cpu-large with Cirun #21
Conversation
…nda-forge-pinning 2024.02.23.09.37.40
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@RaulPPelaez, push an empty commit here to test the Cirun triggers. Thanks! |
Seems to be running. Should I merge #19 here or the other way around? |
Whatever you prefer, this PR is here for your convenience. Pick one and iterate there :) |
@jaimergp could you clarify what this means? I cannot longer call Also I cannot manage to make the CI run in #19 so I will move the commits here... |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/cutlass-feedstock/actions/runs/8018330283. |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/cutlass-feedstock/actions/runs/8018331935. |
…nda-forge-pinning 2024.02.23.09.37.40
Running into:
I'm not sure how linking the driver would have worked on azure (though we also haven't been able to build anything >=v3.2), but by itself, this looks like we might have to use the gpu runner after all? |
I believe it should be enough to add cuda-driver-dev as a dependency. Lets try |
Correct. GH prevents workflows from modifying other workflows in a PR for security reasons. Since cirun requires GHA workflows and rerendering happens via GHA jobs under the hood... we hit that limitation. We might come up with a workaround, but for now this is what we have. You'll need to rerender locally with |
Adding cuda driver was not enough. I can see it installed, but the same error arises. |
Neither If so, then I think we do need |
To the best of my knowledge, I am unaware of such thing as |
Is it coming from the CMake |
Haven't looked into how cutlass's CMake works, but this preprocessing log seems fishy
|
@@ -26,6 +25,7 @@ requirements: | |||
host: | |||
- cudnn | |||
- libcublas-dev # [(cuda_compiler_version or "").startswith("12")] | |||
- cuda-driver-dev # [(cuda_compiler_version or "").startswith("12")] |
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.
This seems to be correct to me, if you need the header and to link to libcuda.so
.
Thanks for your input @leofang!
Well, cutlass if from NVIDIA, so in some way yes. Looking at the source upstream now, I see that cutlass does a sort of CMake-wrapper around the driver library. It looks like we need to teach the search just above to look in the right place for finding |
Actually I am with @leofang here, wth is libcuda_driver.so? I cannot find references to it online. Maybe setting CUDA_TOOLKIT_ROOT_DIR to CONDA_PREFIX? |
Click the first link in my comment |
Again, NVIDIA does not ship libcuda_driver.so. If this is from CUTLASS CMake, you need to ask CUTLASS folks about how to patch/fix it. |
Note that only builds triggered by maintainers of the feedstock (and core)
who have accepted the terms of service and privacy policy will run
on Github actions via Cirun.
at https://github.com/Quansight/open-gpu-server
Also, note that rerendering with Github actions as CI provider must be done
locally in the future for this feedstock.
Closes #19