Closed xylar closed 1 year 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
@conda-forge-admin, please rerender
The aarch64 (and maybe ppc64le) failures are likely because of tests that can't be run when cross-compilinig.
The osx-arm64 failure is:
/Users/runner/miniforge3/conda-bld/airflow-split_1675310198691/_build_env/etc/conda/activate.d/activate_clang_osx-arm64.sh: line 109: /Users/runner/miniforge3/conda-bld/airflow-split_1675310198691/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_place/bin/env: Bad CPU type in executable
I don't understand that one at all. It would seem like a bad bin/env
is getting installed but it seems like the problem arises before even running install_airflow.sh.
Changing the shebang in install_airflow.sh
from #!/usr/bin/env bash
to #!/bin/bash
didn't make a difference (no surprise).
I'll need to debug more at a later time. Suggestions welcome!
I am not knowledgeable at all in cross-compiling. All I notice is the failure says "Bad CPU in executable". Could this have something to do with 32-bit versus 64-bit?
For example, https://www.technewstoday.com/bad-cpu-type-in-executable/
@nickpowersys, the error is not to do with 32-bit vs. 64-bit (though that was a good guess). It is because we are compiling on osx-64 but I believe bin/env
is being run that is osx-arm64. I'm just not sure how to fix it.
@conda-forge-admin, please rerender
Checklist
conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)closes #101