Interesting, so if I run this manually in the same chroot, I can make it go away simply by changing the list of test files presented to pytest. So this isn’t a chroot issue per se. We are confusing pytest with our sources.