-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix and improve static builds #2755
Conversation
This is back to the error we get on As an alternative, in conda-forge/micromamba-feedstock#136 I try to allow a way to use a local source. It works locally. |
c2a694d
to
186f4af
Compare
@pavelzw any idea why we are seeing mamba-org/setup-micromamba#68 on OSX builds? |
Great, this works! I added |
This reverts commit 3b1a7d2.
The remaining failures are unrelated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great thanks! Is the umamba_tests
failure on macos unrelated too?
I created mamba-org/setup-micromamba#130 |
It was a spurious failure. |
* Check that CI fails * Run CI through conda-forge script * Run conda-forge script in feddstock dir * Try setting mamba source visible to conda-forge script * Fix feedstock patch path * Checkout TMP AntoinePrv repo * Don't template micromamba-feedstock * Fix checkout ref * Extract static package * TMP debug OSX build * Set OSX out dir * Disable cleanup * Run Linux ppc64le and aarch64 builds on emulated arch * Try running python on fedora * Run docker in docker * Try ubuntu * Change repo to conda-forge * Revert "Check that CI fails" This reverts commit 3b1a7d2. * Remove unused recipe fork
No description provided.