-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Rebuild for CUDA 12 w/arch support #51
Rebuild for CUDA 12 w/arch support #51
Conversation
The transition to CUDA 12 SDK includes new packages for all CUDA libraries and build tools. Notably, the cudatoolkit package no longer exists, and packages should depend directly on the specific CUDA libraries (libcublas, libcusolver, etc) as needed. For an in-depth overview of the changes and to report problems [see this issue]( conda-forge/conda-forge.github.io#1963 ). Please feel free to raise any issues encountered there. Thank you! 🙏
…nda-forge-pinning 2023.08.30.17.25.59
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 ( |
Let's hold until 23.08 update is in 😄 |
Yeah removed automerge here and added to your PR That said, 23.06 does support CUDA 12 (and was migrated before). This just adds other architectures |
Ah, maybe lets land this then first? Would be nice to have CUDA 12 23.06 packages 😄 |
Ok either way |
Should avoid no-op migrations that do this by default.
Hopefully fixes the memory errors on arch builds.
@conda-forge-admin, please re-render |
Saw a memory issue in the arch builds. Added changes to clean up the CI images If that doesn't work, we may need to add a swap file ( conda-forge/conda-smithy#1751 ) (pending a conda-smithy release) |
…nda-forge-pinning 2023.08.30.17.25.59
Yea, looks like the memory issues continue. How about only building the tests if we're in linux_64? Mostly wanted to just confirm dependency upgrades aren't breaking things. |
@conda-forge-admin, please re-render |
…nda-forge-pinning 2023.08.31.12.59.55
@conda-forge-admin, please re-render |
…nda-forge-pinning 2023.08.31.12.59.55
Looks like there is a new conda-smithy release. So tried added the swap file change
Would also be ok with that if this doesn't work |
azure: | ||
free_disk_space: true | ||
settings_linux: | ||
swapfile_size: 10GiB |
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.
Still seeing the same error. Not sure what we should bump this too. Any thoughts?
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.
I'm really unsure where there's a lot of "weird environment" in the loop here. The fact that different components are failing with signal 11 points to environment from my perspective.
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.
IIUC the feedstock is using emulation for arch builds. Could that be an issue? Should we use cross-compilation or native builds?
librmm-feedstock/conda-forge.yml
Lines 9 to 11 in f0423fb
provider: | |
linux_aarch64: azure | |
linux_ppc64le: azure |
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 is only building tests to ensure dependency version changes don't break downstream usage of RMM headers. I would prefer to keep the setup as simple as possible where the easiest path forward would possibly be to just only build the tests on linux-64?
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.
That sounds ok to me
🎉 @jakirkham @leofang could one of you take a look so we can land this, then land the 11.8 rebuild, then the 23.08 upgrade? 😆 |
Sorry for delay, LGTM |
Thanks Keith & Leo! 🙏 |
This PR has been triggered in an effort to update cuda120.
Notes and instructions for merging this PR:
Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.
Here are some more details about this specific migrator:
If this PR was opened in error or needs to be updated please add the
bot-rerun
label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun bot
in a PR comment to have theconda-forge-admin
add it for you.This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/6028280553, please use this URL for debugging.