-
-
Notifications
You must be signed in to change notification settings - Fork 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
bump to version 0.4.3 #12
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 ( |
Please re-render with |
I'm getting an error with conda-smithy 1.3.2:
|
OK, looks like I had an old version of conda-build-all (0.11). Perhaps that requirement should be added to the conda-smithy recipe? |
Rerender in #13. I'll rebase this PR once that is merged. |
Sorry I missed that. Glad you got it sorted though. The situation is more that to use |
Appveyor is failing because when activating the environment, Seems related to this issue, and the fix there is basically "make your It seems fixing this would require modifying the AppVeyor scripts somehow... any ideas on that? |
Sorry @jakevdp but I have no idea on both cases. Maybe we can work around the AppVeyor error... @msarahan do you have any idea why this is affecting only PY27? I lost track of things but it seems like the feedstoscks are still downloading Edit: xref conda-forge/conda-forge.github.io#252 |
IIUC there was some bad interaction between |
Appveyor still failing on 2.7, due to the PATH being too long. |
Looks like some difference in how paths are specified between |
FYI, AppVeyor has miniconda built-in, so maybe conda-forge should be using their version? appveyor/ci#359 |
Like I said above
I do use it in my non-conda-forge builds and I do remember @jjhelmus implementing that here. But since |
We changed to AppVeyor's included Miniconda in staged-recipes. It was kind of a mess as it is pretty out-of-date in some cases. It was suggested that we do the same in feedstocks. However, the person suggesting it changed their mind due to some issues they encountered. So we skipped it. Given using Miniconda is already a problem as we spend a couple of minutes just updating from defaults packages to conda-forge packages and sometimes (more frequently of late) run into connectivity issues by slamming Anaconda.org in this way, the general feeling is we should have our own installer to cutdown build time and limit this impact. The situation with using an outdated copy of Miniconda will undoubtedly be no different in this respect. We packaged everything needed to do this. Someone even got the basics for an installer together during a Hackathon at SciPy. It was transferred to a repo here. Though there are a number of important issues we need to address before we can proceed. Help on any of these would be appreciated. |
It is a pity you think that is messy, or worse, have our own installer. That kind "forkish" behavior is the one that drivers people away. BTW the default AppVeyor miniconda works wonders in all my other projects. Including building with Ping @asmeurer who is also puzzled with some the the weird decision in conda-forge in conda-forge/conda-forge-build-setup-feedstock#38 |
Is there any significant difference in what you get if you (a) download and install miniconda-latest or (b) use an old miniconda and run |
BTW this is what I use and I do not think it is messy: environment:
matrix:
- PYTHON: "C:\\Miniconda-x64"
PYTHON_VERSION: "2.7"
PYTHON_ARCH: "64"
- PYTHON: "C:\\Miniconda"
PYTHON_VERSION: "2.7"
PYTHON_ARCH: "32"
init:
- "ECHO %PYTHON_VERSION% %MINICONDA%"
install:
- "set PATH=%PYTHON%;%PYTHON%\\Scripts;%PATH%"
That part is easily fixed by a |
Not to my knowledge. My Other auto-build conda packages projects work just fine that way. |
I had heard that Miniconda was going to change to install conda into a separate environment, but I just tested the latest Miniconda OS X installer and it didn't do that, so I'm not so sure. |
Can someone restart the AppVeyor build here? |
Just did. Btw you should have AppVeyor rights here to restart it too. Let me know if that is not working. |
The failure will be resolved by re-rendering with |
Appveyor builds completed after 10 hours in the queue, but one hit a network error. Since there's no way for Appveyor to restart a single job I restarted them all. Sigh... |
You're not alone. Hence the long queue. 😒 Trying to track this down with upstream. ( https://github.com/Anaconda-Platform/support/issues/78 )
Asked upstream for this feature. ( appveyor/ci#1114 ) |
Another single network error in Appveyor after half a day in the queue. I'll restart all the builds again, since that's the only recourse. This is seriously trying my patience... |
Given the constraint these two trials put on the probability of failure and duration of the queue, I could model it as a multinomial process compute an expectation value for how long this will take to finish... but that would probably just depress me. Or maybe I should just merge? |
@jakevdp just merge it as you can restart it on master to get the missing package to be uploaded. You already know that the build will pass and that error is only network issue. Unfortunately an |
OK! |
FWIW it seems the merge passed on the first try. |
yep, I noticed that 😄 |
No description provided.