-
Notifications
You must be signed in to change notification settings - Fork 71
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
Lots of "export path <path> doesn't exist" error messages on Windows Server #207
Comments
I just tried this myself, and I wasn't able to reproduce the problem. I've even tried setting up a Python 3.6 virtual env and running inside there. (I'm on Arch Linux, where the current Python version is 3.8.1.) If you run it on a different machine, do you get a different result? Any suggestions for repro steps I could try? |
Could you give us the output of the following:
|
I'd guess this is because of how paths differ on Windows and Linux. Windows uses backslashes and this might be the reason why paths are not properly found. |
Peru has always supported Windows (AppVeyor CI testing etc), so the problem isn't going to be that nothing works on Windows :) I've run Do you have another Windows machine that you could try this on? If you find that it repros on one machine and not another, could you try to find steps to make it repro on the second machine? |
I got Selenium IDE sources from their release branch https://github.com/SeleniumHQ/selenium-ide/tree/v3 and try to "peru sync" it on Windows Server under Git Bash. According to travis.yml I have to first install Python 3.6.0, then use it to install peru:
then I have to "peru sync". The peru.yaml file goes like this:
When I
peru sync
(with repository root being the current directory) there's an error message like this:for each of the "atoms" the peru.yaml
This looks working in Selenium IDE CI build.
What am I doing wrong?
The text was updated successfully, but these errors were encountered: