-
-
Notifications
You must be signed in to change notification settings - Fork 13
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 to 0.6.2 #28
bump to 0.6.2 #28
Conversation
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 ( |
…da-forge-pinning 2021.01.09.18.21.49
Aside from the missing aarch-builds for |
It looks great to me! Thanks a lot @h-vetinari for the help with the new release. Just a couple of questions:
|
Hey @bstellato, thanks for the feedback!
#24 had failing tests (those happened across all current PRs on 0.6.1 for reasons I could not determine); as soon as this PR is through, I'll rebase #24 and that shouldn't be an issue.
These aren't failing tests, just missing builds because the newly-added dependency
It's still in use for ppc64le builds. Not sure what agreement was reached between conda(-forge) and travis, but all transitioning projects (that I know of) only do so because the free tier has way too little CI capacity to support development. |
If you restart this PR in about an hour (once the builds on for qdldl are through and the builds have reached the server cache), the CI should go green, and the PR can be merged - just in my timezone it's a bit late already to wait for that. ;-) |
Unfortunately, we have what looks like real test errors on ppc64le (aarch still didn't pick up the dependency):
I'm still going to merge this, and we can figure out aarch support independently of #24 an #26. |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)Since the migrator hasn't come past yet, do it manually