Hi team, I have a case where running some test usi...
# generalw
wide-zoo-86070
04/21/2022, 8:46 PMHi team, I have a case where running some test using pants fails. But if I use
--no-process-cleanup__run.sh__run.sh./pants testwide-zoo-86070
04/21/2022, 8:47 PMThe reason it fails from pants test, is that it cannot find a module. It does not happen if I just use
__run.sh.w
witty-crayon-22786
04/21/2022, 8:57 PMdo you have any environment variables set in your shell which might impact `__run.sh`…? PYTHONPATH in particular. the sandbox will prune those, but it uses a different implementation than
__run.shwitty-crayon-22786
04/21/2022, 8:57 PM(check
envw
wide-zoo-86070
04/21/2022, 9:05 PMI do have have a couple var in PYTHONPATH. but they are the exactly same as PEX_EXTRA_SYS_PATH in the __run.sh.
w
witty-crayon-22786
04/21/2022, 9:07 PMwould try clearing the PYTHONPATH inside of
__run.shw
wide-zoo-86070
04/21/2022, 9:08 PMso the pants does not use __run.sh?
w
witty-crayon-22786
04/21/2022, 9:08 PMcorrect.
witty-crayon-22786
04/21/2022, 9:09 PMit would be good to make those consistent: but currently there is no shell used at all when we invoke processes (unless
@ruleswitty-crayon-22786
04/21/2022, 9:11 PMbut avoiding assuming a shell is good… so if doing more filtering of your
env__run.shw
wide-zoo-86070
04/21/2022, 9:12 PMok that makes sense. What about the the env if a process got created (i.e. subprocess.run) in a test running by pants? i feel that the env does not passed to the new process.
w
witty-crayon-22786
04/21/2022, 9:14 PMpants itself only handles passing environment variables to pytest: and it won’t pass ~anything other than those that have been configured: https://www.pantsbuild.org/docs/python-test-goal#setting-environment-variables
if your test is spawning a subprocess, it would need to propagate the env itself
🙌 2
h
happy-kitchen-89482
04/22/2022, 10:17 AMI've just found a case where a resolve fails, but if I run it with its
__run.sh2 Views