Latest AppVeyor added cygwin and that broke my current workflow
Hi,
I have a complicated work-flow that uses conda to test software builds on Windows. The latest AppVeyor update seems to be using Cygwin as the default shell, but that broke the use of conda to build the software:
https://ci.appveyor.com/project/comtbot/conda-recipes/build/1.0.418/job/6lbtfkxb6o1hiq7k
While I am trying to address the origin of the issue and get conda working with Cygwin, I am wondering if it is possible to use the old AppVeyor setup (or disable cygwin)?
Thanks,
-Filipe
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 04 Jun, 2015 10:29 PM
Hi Filipe,
Could you please elaborate how installing Cygwin broke your build? It was just installed (basically unpacked) to C:\cygwin folder without adding anything into PATH.
Anyway, you can just add a command line deleting that folder recursively.
- Feodor
2 Posted by Filipe Pires Al... on 04 Jun, 2015 10:51 PM
To be honest I have no idea!
conda_build calls git via a python subprocess, and, before cywing, that
worked out fine. After Cygwing, somehow, cygwin git is called and it
returns this error:
subprocess.CalledProcessError: Command '['C:\\cygwin\\bin\\git.exe',
'clone', '--recursive',
u'C:/conda/conda-bld/git_cache/__github.com_axiom-data-science_pyaxiom',
'C:\\conda\\conda-bld\\work']' returned non-zero exit status 128
Command exited with code 1
Deleting the folder crossed me mind. I will try it. However, I want to
"fix" this (maybe it is a bug in conda, dunno) so I can use Cygwin in the
future.
Thanks!
-Filipe
Support Staff 3 Posted by Feodor Fitsner on 04 Jun, 2015 11:17 PM
Yeah, let me know what you'll find.
- Feodor
4 Posted by Filipe on 04 Jun, 2015 11:20 PM
Removing the Cygwin directory restored the "status quo." I will play around to get it working without removing (because I do want to use the new staff ;-) and I will report back here.
Thanks!
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:56 AM.