You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the investigation of #6828, it was difficult to parse log output for legitimate error messages because of the variety of messages printed directly to stderr from passing tests. For example, pants_test.backend.python.tasks.test_python_distribution_integration.PythonDistributionIntegrationTest#test_binary_dep_isolation_with_multiple_targets prints unconditionally:
Traceback (most recent call last):
File ".bootstrap/_pex/pex.py", line 349, in execute
File ".bootstrap/_pex/pex.py", line 281, in _wrap_coverage
File ".bootstrap/_pex/pex.py", line 312, in _wrap_profiling
File ".bootstrap/_pex/pex.py", line 394, in _execute
File ".bootstrap/_pex/pex.py", line 506, in execute_entry
File ".bootstrap/_pex/pex.py", line 513, in execute_module
File "/opt/twitter_mde/package/eepython27/e4cdee382b83e4185a42b54120b1b11021cec1d8285cc9023ef2dabf8c9af24d/lib/python2.7/runpy.py", line 192, in run_module
fname, loader, pkg_name)
File "/opt/twitter_mde/package/eepython27/e4cdee382b83e4185a42b54120b1b11021cec1d8285cc9023ef2dabf8c9af24d/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "python_distribution/fasthello_with_install_requires/main.py", line 8, in <module>
ImportError: No module named pycountry
The relevant test output from #6828 is in this gist, but I suspect there are more such tests. We should figure out how to stop or redirect sources of printing directly to stderr in these tests to make it easier to read logs.
One relevant point which is also visible in that gist is that pex will unconditionally print the output of building a python_dist() which has native Extensions in its setup.py directly to stderr, and this has generated encoding errors internally in the past (where if the compilation failed, you couldn't see the error, because pex would print directly to stderr, but the act of printing to stderr raised an exception). That part would require a small and I believe uncontroversial change somewhere around this line of pex/installer.py.
The text was updated successfully, but these errors were encountered:
In the investigation of #6828, it was difficult to parse log output for legitimate error messages because of the variety of messages printed directly to stderr from passing tests. For example,
pants_test.backend.python.tasks.test_python_distribution_integration.PythonDistributionIntegrationTest#test_binary_dep_isolation_with_multiple_targets
prints unconditionally:The relevant test output from #6828 is in this gist, but I suspect there are more such tests. We should figure out how to stop or redirect sources of printing directly to stderr in these tests to make it easier to read logs.
One relevant point which is also visible in that gist is that pex will unconditionally print the output of building a
python_dist()
which has nativeExtension
s in its setup.py directly to stderr, and this has generated encoding errors internally in the past (where if the compilation failed, you couldn't see the error, because pex would print directly to stderr, but the act of printing to stderr raised an exception). That part would require a small and I believe uncontroversial change somewhere around this line ofpex/installer.py
.The text was updated successfully, but these errors were encountered: