-
-
Notifications
You must be signed in to change notification settings - Fork 519
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
Report subprocess exit code when invocation fails #192
Comments
Original comment by @mgedmin Does this look about right?
If yes, I'll fix up the tests and submit a proper PR. |
Original comment by @hpk42 Agreed, care to submit a PR? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Story: A Jenkins job running tox failed in the 'pip install' step, without a clear error message. After some headscratching I decided to look at dmesg and saw that the server ran out of memory and the OOM killer decided to kill some processes.
Now if tox reported actual exit statuses instead of just saying "invocation failed", I might've seen that pip did not exit with an error code but rather was killed by a signal. That would've been a useful Clue to have.
The text was updated successfully, but these errors were encountered: