Closed ngam closed 2 years ago
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.
@conda-forge-admin, please rerender
@mkitti
Is the plan that we merge this and then see if scipy starts working again?
Is the plan that we merge this and then see if scipy starts working again?
No, we can just it locally/separately. Download artifacts, etc. unless people want to merge this...
What is the best way to download and install a package built in this PR?
What is the best way to download and install a package built in this PR?
Needs the following in conda-forge.yml
plus a rerender:
# TODO: remove after debug
azure:
store_build_artifacts: true
What is the best way to download and install a package built in this PR?
Needs the following in
conda-forge.yml
plus a rerender:# TODO: remove after debug azure: store_build_artifacts: true
Already done.
What is the best way to download and install a package built in this PR?
Here: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=562537&view=artifacts&pathAsName=false&type=publishedArtifacts (hover over and go to the three vertical dots on the very right to download)
Once downloaded you can either:
-c yourchannel
mamba install thepathtobz2
Not if you install directly, it won't install the deps automatically (I usually install the latest from conda-forge, then install a local one)
I will test arm64 for you now
builds are available https://anaconda.org/ngam/openblas/files
Matrix isolating the errors on osx-64: https://github.com/ngam/test_openblas_scipy/
Conclusion: as rgommers said, the errors are due to fortran updates (or more precisely, the automated updates in this PR).
Already done.
Sorry I didn't check this (was on a phone...), seems you're well on top of things. ;)
Once downloaded you can either:
- upload to a personal channel and then pull down like usual with
-c yourchannel
Note that you can use
conda install -c /path/to/where/you/unpacked/the/artefact openblas
if you download it directly.
Conclusion: as rgommers said, the errors are due to fortran updates (or more precisely, the automated updates in this PR).
Do we have any idea/intuition why a compiler upgrade would break this (well, aside from compiler regressions)...?
No idea, back to @rgommers to evaluate...
Closing since this issue is nothing to do with our intentional updates and it is just compilers, so upstream will fix.
https://github.com/conda-forge/openblas-feedstock/pull/146
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)