-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
numexpr v2.8.4 #45
numexpr v2.8.4 #45
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 ( |
@@ -7,9 +7,9 @@ channel_targets: | |||
cxx_compiler: | |||
- vs2019 | |||
mkl: | |||
- '2022' | |||
- '2022.1.0' |
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.
We need to pins those via a local conda_build_config.yaml
file or they'll be removed in the next re-render.
Try a file with:
mkl:
- 2022.1.0
mkl_devel:
- 2022.1.0
in the recipe folder and then re-render.
Is there a way to pin those for just the windows builds?
The Linux and osx builds don't need this workaround.
I mentioned this in another PR, but ideally we could merge this to unblock
upstream packages. And then eventually resolve the issue in libblas and
rerender to remove the pin.
…On Mon, Apr 3, 2023, 06:59 Filipe ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In .ci_support/win_64_mkl_supportmklnumpy1.21python3.10.____cpython.yaml
<#45 (comment)>
:
> @@ -7,9 +7,9 @@ channel_targets:
cxx_compiler:
- vs2019
mkl:
-- '2022'
+- '2022.1.0'
We need to pins those via a local conda_build_config.yaml file or they'll
be removed in the next re-render.
Try a file with:
mkl:
- 2022.1.0mkl_devel:
- 2022.1.0
in the recipe folder and then re-render.
—
Reply to this email directly, view it on GitHub
<#45 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPRFHY3CLFLR4I4NKAJFTW7K3TFANCNFSM6AAAAAAWPHQ64A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
mkl: # [win]
- 2022.1.0 # [win]
mkl_devel: # [win]
- 2022.1.0 # [win] This should work (untested)! |
Appears to have worked perfectly, thanks! |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
@ocefpaf any ideas? the build seems stuck in a loop trying to upload:
|
Not sure. Let's wait for the re-tries. |
They have all failed 😞 |
Looking at a few other feedstock pipelines it appears this is not an issue with this feedstock, other main branch builds have failed to upload with the same error. |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)