You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the installation of Mambaforge in the logs indicates that your copy of staged-recipes is not up-to-date; scripts were updated to use Miniforge a few months ago; try pulling the latest copy and rebasing
I'm unsure about support for running build-locally.py when the host is osx-arm64; that represents a configuration that isn't tested, AFAIK; maybe this can be worked around by exporting CONDA_SUBDIR=osx-64 prior to running the script?
sudo shouldn't be necessary, but maybe there are reasons (perhaps elaborate?)
I started using sudo as some directories for the SDK could not be created.
Is there a workaround to test this? I have pushed a couple of buggy versions (see conda-forge/admin-requests#885 (comment)) because I am not able to test it locally. VMWare could work?
How people usually test the build to avoid pushing buggy versions
If specifically trying to test the hypso recipe - it is a noarch recipe, so linux-64 build is all that matters and that will run through Docker (if you have it installed and running).
Otherwise, light trial-and-error debugging directly in a PR is fine. We frequently deal with recipes that need troubleshooting after version bumps, and I'd be surprised if anything less than 90% of that is done directly on GitHub (i.e., never touches local).
Note, occasionally you may want to inspect/locally test artifacts, which can be enabled by adding to the feedstock's conda-forge.yml:
azure:
store_build_artifacts: true
I believe this requires a rerender to take effect.
Bug:
@conda-forge/staged-recipes
Tutorial to Test locally: https://conda-forge.org/docs/maintainer/adding_pkgs.html#running-tests-locally-for-staged-recipes
Error: KeyError: 'https://conda.anaconda.org/conda-forge'
The text was updated successfully, but these errors were encountered: