Appveyor x64 py27 builds failing
See original GitHub issueI’ve submitted a number of revisions and refactors that are dying because the x64
, py27
build on Appveyor is failing to start conda
. Example:
call %CONDA_INSTALL_LOCN%\Scripts\activate.bat
failed to create process.
failed to create process.
failed to create process.
'"C:\Miniconda-x64\Scripts\\..\python"' is not recognized as an internal or external command,
operable program or batch file.
conda update --yes --quiet conda
'conda' is not recognized as an internal or external command,
operable program or batch file.
Some example pulls are: python-engineio
, setuptools-git
, pytimeparse
, and pysocks
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Build works for Py27, Py27-x64 and Py34. But fails on Py34-x64 ...
Hello,. When I start a build it works for Py27, Py27-x64, Py34, but fails on Py34-x64. The fail reason is appears to be...
Read more >tox 3.8 crashes on Appveyor · Issue #1227 · tox-dev/tox - GitHub
In the h5py project, all the builds on Appveyor recently started failing. This seems to coincide with the release of tox 3.8.0, ...
Read more >Problems building Numpy with OpenBLAS for Windows x64(aka
A. Is there any other way to build Numpy with OpenBLAS on windows x64 other ... by any compatible compiler (eg: msvc90 for...
Read more >appveyor.yml · 06b4fa06ce0580f13e077cff6947108c7976bbd7 ...
For now, Appveyor will only build PR commits and not commits to master or ... SDK v7.0 MSVC Express 2008's SetEnv.cmd script will...
Read more >conda-build Documentation
Choose to install X64 Compilers and Tools. Install Service Pack 1. ... sample issue if the conda-build command fails. ... such as "py27"....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also have restarted any builds that appeared to be affected by this issue.
Upstream has rolled the image back for now. FWICT this is working correctly on running builds. They will push a new fixed image tomorrow evening. More details on the upstream ticket.
For now, would recommend restarting any failing builds to get them back in the queue. They should behave normally once started.
Thanks for raising to our attention, @pmlandwehr.