Refresh CUDA 12 migrator#26
Conversation
|
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 ( |
|
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues. Please check the output logs of the latest rerendering GitHub actions workflow run for errors. You can also ping conda-forge/core for further assistance or try re-rendering locally. This message was generated by GitHub actions workflow run https://github.com/conda-forge/qiskit-aer-feedstock/actions/runs/7498758708. |
Pull in latest changes from `conda-forge-pinning`. https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/cbccb41e313c017c1ad15db6c287e87aa57d54dd/recipe/migrations/cuda120.yaml
|
@conda-forge-admin , please re-render |
…nda-forge-pinning 2024.01.11.21.29.17
|
This is passing! 🎉 @conda-forge/qiskit-aer this is ready for review 🙂 |
|
Thanks Bas! 🙏 |
Recently the CUDA 11.8 migrator was closed out ( conda-forge/conda-forge-pinning-feedstock#5340 ). As part of that it was determined a small updated was needed to the CUDA 12 migrator ( conda-forge/conda-forge-pinning-feedstock#5340 (comment) ). While this largely works for most feedstocks without changes, those that have
use_local: truewill have issues with re-rendering until the CUDA 12 migrator they have is updated. This PR pulls over those updates to fix re-rendering on the feedstock. Please let us know if you have any other questions.Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #25.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.
Fixes #25