8.0.0 + pyargs + permissions causes failures

[pulkin]

Example of a successful test-install build on 7.4.4:

https://github.com/pulkin/pyteleport/actions/runs/7603885071/job/20706143053

On 8.0.0 it starts looking into inaccessible folders and fails right away:

https://github.com/pulkin/pyteleport/actions/runs/7733355863/job/21085241736

[bluetech]

This has been reported a few times already. The previous cases were legitimately bad ideas, running tests from /tmp. But since it seems like a common issue, we probably should make it work.

The easiest thing is to simply ignore files/dirs which raise a permission error, however I don't like this because it may silently skip over files which are meant to be included and really have wrong perms.

Another easy option is to warn and ignore, but the people who report this probably don't want the noise.

The problem started happening in pytest 8 because of the Session collection changes. Previously Session would collect the initial files itself, and thus could filter out non-matching files early. Now Session only collects the initial Directorys and then does a "matchnodes" pass after the fact, which means some files now get stat'ed when they previously weren't.

With some effort we could probably go back to avoiding stats on files that are going to get discarded anyway. However it is probably too big a change for 8.0.x so will only be fixed in a feature release.

[pulkin]

I am all ears if you come up with a solution to test an installed package in my case. I used cd / to distance from my src folder as far as it is possible before running pytest.

[bluetech]

I do recommend cd'ing into some empty directory your user owns, or at least /var/empty if you need something ready made.

[pulkin]

To whomever interested, I did this

pulkin/pyteleport@8a5e87c

Creating an empty subfolder in the repo folder did not work because pytest can still find setup.py and use repo files. So you have to create an empty folder side-by-side and test from there.

[KellyP5]

I too am experiencing similar issues, am curious about a way forward. Given my use case, I do not have the option of creating a directory and cd'ing into it given my working environment.