https://pantsbuild.org/ logo
Join Slack
Powered by
Does anyone know/remember if we decided to strip `...
# development
w
Does anyone know/remember if we decided to strip 
extra_env_var
from pytest stdout (or maybe it's a pytest thing?) I've got env vars defined in pants.toml, and those show up in the failure stdout when I do a 
print(os.environ)
but the test target's 
extra_env_var
don't show up, but they used to in 2.18ish timeline
It might also be related to changing the string to bytes for test result?
My HELLO capture is gibberish - broken at the double slash
Copy code
assert os.environ["HELLO"] == "<https://sureshjoshi.com>"
>       assert False
E       assert False

src/python/helloworld/helloworld/main_test.py:10: AssertionError
----------------------------- Captured stdout call -----------------------------
environ({'TOML': '1', 'HELLO': 'https:.cache/pex_root/venvs/8d2ce9b733dd73a51a1d3e30a92d537f60667cd0/b72759668fd3274d8db09b8c05988c647b091745', '__PEX_EXTRA_SYS_PATH__': 'src/python/helloworld/helloworld', 'PYTEST_CURRENT_TEST': 'src/python/helloworld/helloworld/main_test.py::test_hello (call)'})
hello
'world'
<https://sureshjoshi.com>
- generated xml file: src.python.helloworld.helloworld.main_test.py.wtf.xml -
=========================== short test summary info ============================
FAILED src/python/helloworld/helloworld/main_test.py::test_hello - assert False
6 Views
Open in Slack
PreviousNext
Powered by