We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Looks like there are a few feedstocks configured for GPU runners here. Think some (or all) could move to CPU workers
admin-requests/.access_control.yml
Lines 9 to 12 in 58c6320
Most notably conda-smithy, which is noarch and has no GPU code AFAIK
conda-smithy
noarch
conda-forge-ci-setup does have CUDA dependencies, but likely can be built on a CPU worker instead
conda-forge-ci-setup
Guessing cf-autotick-bot-test-package may still be useful for GPU testing, so we could leave it there
cf-autotick-bot-test-package
The text was updated successfully, but these errors were encountered:
cc @jaimergp
Sorry, something went wrong.
I think this was for testing the rerenders, but afaik conda-smithy is not using it actively either.
No branches or pull requests
Looks like there are a few feedstocks configured for GPU runners here. Think some (or all) could move to CPU workers
admin-requests/.access_control.yml
Lines 9 to 12 in 58c6320
Most notably
conda-smithy
, which isnoarch
and has no GPU code AFAIKconda-forge-ci-setup
does have CUDA dependencies, but likely can be built on a CPU worker insteadGuessing
cf-autotick-bot-test-package
may still be useful for GPU testing, so we could leave it thereThe text was updated successfully, but these errors were encountered: