Skip to content
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

'Failed to create process' #98

Closed
MinchinWeb opened this issue Oct 23, 2015 · 6 comments
Closed

'Failed to create process' #98

MinchinWeb opened this issue Oct 23, 2015 · 6 comments
Labels

Comments

@MinchinWeb
Copy link
Contributor

Using Python 3.5.0 x64 on Windows 10 with Green 2.1.2.

Try to run any green command, and it fails and displays the message Failed to create process.

The issue is present on Green 2.1.1 and 2.1.0, but not Green 2.0.7 (which works fine).

@CleanCut CleanCut added the bug label Oct 23, 2015
@CleanCut
Copy link
Owner

(Sigh) I don't even have access to Windows 10. :-(

@MinchinWeb
Copy link
Contributor Author

Well, maybe I can help more. I can confirm that this isn't an issue with Python 3.4.3. I can also confirm that if I clone the repo and run python setup.py install, green installs and runs fine on Python 3.5. This would point to the .tar.gz file on PyPI; something in the packaging or distribution. Is it time to move to wheels? If you can upload one here, I can try installing it to see if that fixes it.

@CleanCut
Copy link
Owner

There are other failing tests on Python 3.5. Maybe if I fix those on posix, Windows may benefit as well. I really dislike the way green communicates with its subprocesses, but I haven't yet found a better way that works across all versions and platforms without pulling in an external library.

@CleanCut
Copy link
Owner

CleanCut commented Nov 4, 2015

Did the new release fix anything, by chance? I'm trying to put together a Windows 10 VM, but if it's already fixed I won't bother...

@MinchinWeb
Copy link
Contributor Author

green seems to be working for me now. I never figure out what was the root cause of the issue, so I'm not sure what changed. I guess we can close the issue, and I'll let you know if it starts acting up again. Thanks for taking the time to look into it.

@CleanCut
Copy link
Owner

CleanCut commented Nov 4, 2015

No problem. I'm glad it's working for you now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants