-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Bump build number to rebuild osx-64 #21
Conversation
osx-64 build failed when merging into main because libcxx was updated from 16.x.x to 17.x.x between the time of the MR and the merge. libcxx 17.x.x requires MacOS >=10.13 (see conda-forge/libcxx-feedstock#131) My understanding is that a re-render should fix it due to conda-forge/conda-forge-pinning-feedstock#5829
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 ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2024.05.13.13.50.55
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.
LGTM
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was not passing and not merged. |
Travis CI is not very reliable. Switch to azure and cross-compiling for aarch64 and ppcle64
@conda-forge-admin, please rerender |
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
Travis CI is not very reliable and really slow. |
…nda-forge-pinning 2024.05.14.14.54.30
@tschoonj the move to azure for linux aarch64 and ppcle64 went well. |
Checklist
conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)osx-64 build failed when merging into main because libcxx was updated from 16.x.x to 17.x.x between the time of the MR and the merge. libcxx 17.x.x requires MacOS >=10.13 (see conda-forge/libcxx-feedstock#131)
My understanding is that a re-render should fix it due to conda-forge/conda-forge-pinning-feedstock#5829