How can I completely cleanup temporary directories from tmp_path?

[davidsc-unity3d]

This recaps a question I posted on stack overflow https://stackoverflow.com/questions/73888271/pytest-tmp-path-unit-tests-do-not-completely-clean-up-after-themselves

Using this pattern

@pytest.fixture
def config_ini(tmp_path):
    filename = tmp_path / "config.ini"
    fout = open(filename, "w")
    fout.write("myfile")
    fout.close()
    yield filename
    os.unlink(filename)

I can delete all the temporary files for successful tests, meanwhile pytest is keeping the last 3 directories for successful and unsuccessful runs. I'm from the school of thought that tests should completely clean up after themselves, so I'd like a mechanism to delete those directories, and even the files if the test fails, but I haven't figured out how to get this to happen, but on the other hand, maybe I should change my school of thought - its fine to leave some directories around.

The other thing, it seems to run pytest distributed, you have to use a tool like https://pypi.org/project/pytest-xdist/ . I see pytest creates paths like

/blah/blah/dsk3240dl_random_string/pytest_1
/blah/blah/dsk3240dl_random_string/pytest_2
/blah/blah/dsk3240dl_random_string/pytest_3

and it seems to always use the same random string? dsk3240dl_random_string - for the use case of running the same test from two separate processes that don't talk to one another, it seems we could get a collision. That is a weird use case, so it is not supported?

[RonnyPfannschmidt]

Xdist let's each worker have a subdirectory of the main folder

As for deferred cleanup, it's a intentional feature, if stuff unexpectedly passes and/or fails, one can directly dig into the artifacts instead of having to rerun /pause tests

[nicoddemus]

I'm from the school of thought that tests should completely clean up after themselves, so I'd like a mechanism to delete those directories, and even the files if the test fails, but I haven't figured out how to get this to happen, but on the other hand, maybe I should change my school of thought - its fine to leave some directories around.

Personally I love this feature... I cannot count the number of times I inspect the temporary files to aid understand a failing test.

[davidsc-unity3d]

Personally I like it too. But in our production environment automation runs the tests on machines we don't have access to, it's a great feature for local dev but less so for this particular prod env. It's not clear to me what will run next or concurrently on these machines, hence the hesitation about tmp_path