-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Rerendering locally with conda-smithy fails #217
Comments
@conda-forge/conda-smithy ? |
You need to add a 11.8 at https://github.com/conda-forge/pytorch-cpu-feedstock/blob/main/.ci_support/migrations/cuda120.yaml#L53-L54 This is why I was skeptical of updating the migration_number conda-forge/conda-forge-pinning-feedstock#5121 and preferred a new migrator. cc @jakirkham |
Not sure that link was intended (if it was I'm not following). Think you are referring to PR ( conda-forge/conda-forge-pinning-feedstock#5340 ) where the 11.8 was added to the CUDA 12 migrator Generally conda-smithy does the right thing as pointed out by Axel and later confirmed by me in this thread ( conda-forge/conda-forge-pinning-feedstock#5340 (comment) ) There are two cases we have seen where re-rendering out of the box doesn't work:
For 1, I sent a bunch of PRs xref'd at the bottom that manually fix those feedstocks. Nearly all are merged. The 2 remaining we could merge if we like. Have left that task to maintainers for now 2 is what Julien ran into. All that is needed is to purge conda-smithy's stale migrator cache so it refreshes. In cases where there is no cache (like the bot) this issue doesn't occur On my system purging conda-smithy's migrator cache looks like this
Ideally conda-smithy could detect if the cache is stale and do this for us |
As of 99445d4, re-rendering locally using
conda-smithy==3.30.4
fails:Full log
Yet, I have been able to re-render with the following naive changes to conda smithy as of conda-forge/conda-smithy@a8d9761 to work around the observed error:
Work around for
conda-smithy
For convenient to skip version verification which is 0.0.0 when built from sources:
This produces the following changes, but I am unsure about their validity:
Result of rerendering
I do not know whether this is an issue with conda-smithy or this feedstock yet.
The text was updated successfully, but these errors were encountered: