numexpr v2.8.4

[apmorton]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-webservices]

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 (recipe) and found it was in an excellent condition.

[ocefpaf]

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.

[apmorton]

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: ***@***.***>

[ocefpaf]

Is there a way to pin those for just the windows builds?

mkl:  # [win]
  - 2022.1.0  # [win]
mkl_devel:  # [win]
  - 2022.1.0  # [win]

This should work (untested)!

[apmorton]

Appears to have worked perfectly, thanks!

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[apmorton]

@ocefpaf any ideas? the build seems stuck in a loop trying to upload:

ERROR getting output validation information from the webservice: JSONDecodeError('Expecting value: line 1 column 1 (char 0)')
copy results:
{}
Failed to upload due to copy from staging to production channel failed. Trying again in 10 seconds

[ocefpaf]

Not sure. Let's wait for the re-tries.

[apmorton]

They have all failed 😞

[apmorton]

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.

See: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=683522&view=logs&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=e5c8ab1d-8ff9-5cae-b332-e15ae582ed2d

[apmorton]

See: conda-forge/status#143