-
Notifications
You must be signed in to change notification settings - Fork 21
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
Ensure proper execution of subprocesses on MS Windows #22
Comments
But this masks an issue, which is documented in issue #22.
What do you mean? We've been using this for quite some time and it seems to work fine. I'm confused by the commit referenced above as well. The Appveyor tests have been fixed in that failed tests are now reflected in the return code. What was the above commit fixing? |
Gabe: I didn't realize that your commits fixed the return code. But in any case --Bill On Wed, Jul 6, 2016 at 4:48 PM, Gabriel Hackebeil [email protected]
|
Agreed. Maybe we should rename this ticket to reflect that. The problem is with output redirection, not the return code.
|
The subprocess.run command either does not return the appropriate value or it does not generate output. This branch is focused on resolving this discrepancy.
The text was updated successfully, but these errors were encountered: