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
test_distutils is too verbose on Windows #74503
Comments
test_distutils should only dump stdout/stderr on compilation failure, but hide them on success (by default). Example of output: http://buildbot.python.org/all/builders/x86%20Windows7%203.x/builds/588/steps/test/logs/stdio 0:58:52 [277/405/1] test_distutils passed (124 sec) -- running: test_tokenize (322 sec) D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\build\test_python_204>exit 1 D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\build\test_python_204>exit 0 |
The problem here I think is that distutils itself should only dump stdout/stderr on failure, but because of how it spawns processes it never actually captures the output from external tools. We really need to update distutils's spawn() function to use subprocess. That would also resolve a handful of other issues. |
Hum, I would like to see warnings even if the compilation succeed. So I would prefer to only modify test_distutils. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: