-
-
Notifications
You must be signed in to change notification settings - Fork 14
tst: release 1.0.0 #10
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
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 ( |
I started a Travis build on my allocation, in case that lets us jump the queue for OSX builds. https://travis-ci.org/effigies/nipype-feedstock/builds/333382502 |
@conda-forge-admin, please rerender. |
@effigies looks like your build jumped the queue, want to give it another go? If travis passes, we can merge nipy/nipype#2399 and update url/md5 to nipype's release tarball |
Yup. https://travis-ci.org/effigies/nipype-feedstock/builds/333398751 OTOH, the number of nodes running OSX jobs has just been cut by a third. https://www.traviscistatus.com/ |
I think the scheduling algorithm is roughly round-robin on a per-allocation basis, so my top job is on (more-or-less) equal footing with conda-forge's top job. And conda-forge has like 30-40 projects that are sitting and waiting for their turn to be the top job. |
@mgxd Finished. You can release. |
Hey, it passed! @satra @chrisfilo I think you need to merge, and we can get conda builds online. |
OMG - this is happening. |
No description provided.