-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
GPU queue experiments #446
base: gpu-tests
Are you sure you want to change the base?
Conversation
jaimergp
commented
Dec 19, 2022
•
edited
edited
- Add support in conda-smithy for rerenders
- Add support for Cirun on self-hosted GHA runners conda-smithy#1703
- Log in with a conda-forge bot account to configure it with Quansight's OpenStack cloud provider
- Add support for automatic repository registration:
- Enable Cirun app for given repository, on Github end
- Enable Cirun OpenStack-GPU runner for given repository, on Cirun end
- Add support in admin-requests
- Documentation
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 ( |
MNT: Re-rendered with conda-build 3.21.7+119.g1b221ef0, conda-smithy 3.22.1.post.dev3, and conda-forge-pinning 2022.12.19.14.36.50
We need to rebuild the VM images with |
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 ( |
Updated the conda-smithy PR with support to recognize the need for extra docker flags ( |
Co-authored-by: Amit Kumar <dtu.amit@gmail.com>
Good news, the I think there is some issue with SSL downloads inside the Docker instance. With or without GPUs, we are failing to clone the repo that provides the source code to be built:
I have seen this in the two runs that managed to successfully start Another minor detail is that all actions checks are green despite the runner having obviously failed 🤔 See the green checks next to the commit hashes. Have you seen it elsewhere? |
Might be a MTU mismatch. I recall we needed to route things through a VPN tunnel so I guess we are using a lower MTU than default, and Docker is insisting on using 1500. The daemon configuration would have to be amended. |
Well, if you are reading this, please know you are witnessing the first ever conda-build run that has successfully used GPUs in conda-forge 🚀 Relevant block (ignore the warnings, that's OpenCL; omitted here for clarity):
Still a long way to go in terms of access control and so on, but this is a BIG milestone! Thanks @aktech for all the work in the backend! |
Can we try it for CuPy? 🙂 Does it also support aarch64? |
This is nice to see! Thanks Jaime 😄 For CuPy, we can run the tests during the build or on pre-built packages (using |
The server is native x64, but I guess we can cross-compile and/or emulate? I'll try CuPy next week. I am out of hours for this one. |
I am happy to help in any ways, just let me know. (And no rush, ofc!) Right now we use QEMU for aarch64/ppc64le, as it's not possible to cross-compile AFAIK. |