I notice in our integration test infra that integr...
# general
h
I notice in our integration test infra that integration tests aren't hermetic in practice if
use_pantsd=True
, even if
hermetic=True
?
w
They're running in a sandbox with limited env and explicit input files... So unless they depend on
pants.toml
they should be pretty isolated independent of that flag.
h
I'm seeing different in practice
tests that fail unless I set
use_pantsd=False
, and the failure is due to reading the real
pants.toml
w
when you say “real”, do you mean a copy inside the sandbox?
our integration tests transitively depend on
pants.toml
, but that means that it is included in the sandbox
see
./pants filedeps --transitive src/python/pants/option/:integration
for example
h
Presumably copy inside the sandbox, but that is what
hermetic=True
is supposed to finesse, no?
w
whether or not there is a copy inside the sandbox is controlled by the target definition…
python_integration_tests
transitively includes a lot of stuff: https://github.com/pantsbuild/pants/blob/master/pants-plugins/python_integration_tests_macro.py
h
I'm fine if there is a copy inside the sandbox,
hermetic=True
is supposed to tell the pants run under test to ignore it
By setting
--pants-config-files=[]