Closed hhslepicka closed 3 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.
I do have some suggestions for making it better though...
For recipe:
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.
I do have some suggestions for making it better though...
For recipe:
@conda-forge-admin, please rerender
@isuruf this seems good for a review... Thank you for the guidelines on how to do it.
I added tests for the outputs and later I realized that they are likely being covered by blas
.
I can revert https://github.com/conda-forge/lapack-feedstock/pull/49/commits/715f6b337c8580e68e5d58e6076a61546de2e3b4 if that's a problem.
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.
I do have some suggestions for making it better though...
For recipe:
Duplicated tests were reverted via https://github.com/conda-forge/lapack-feedstock/pull/49/commits/3561e257a8c8384da1e1ed46efdfd751a3b8ad03
@isuruf @jakirkham I am not sure why osx_arm64 is no longer recognizing the gfortran compiler. The latest feedstock build worked but for PRs it is failing. It seems unrelated to this change. I will try to find the difference between them but I would appreciate if you could take a look.
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!
@conda-forge-admin, please restart CI
Bit further up in the log:
-- The Fortran compiler identification is GNU 11.0.0
arm64-apple-darwin20.0.0-gfortran: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
Not sure where cc1 is supposed to come from either though.
@h-vetinari the cc1 missing is due to a known issue with gfortran under OS X. The issue and workaround can be found here: https://github.com/conda-forge/gfortran_osx-64-feedstock/issues/11#issuecomment-725890478
I can try to add that to get rid of the warning but my concern is more with the seg fault happening during compilation.
Closes #48
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)