Hi! Is pants injecting some kind of env variable when it is instantiating pytest? I have a test suite that is spinning up a db as part of the test session setup - that can take a few seconds. When the tests run in independant processes, the db might get initialized on the same port despite some port check at start up. The way I was thinking to solve this is to get an int from pants that is different for each parallel test session so that I can increment the port to start the dynamic db on and get for example 17001 and 17002 at start up If people have been solving that differently I am open to other solutions 🙂

Check out `execution_slot_var`: https://www.pantsbuild.org/docs/reference-pytest Example configuration here: https://github.com/pantsbuild/example-django/blob/main/pants.toml#L52

👀