The pytest collection cache wasn't being copied from, resulting in the cached objects being inadvertently modified more than expected. This would manifest as strange errors when you ran something a third time or later, typically from fixture value reuse, and only on tests that had fixtures that were affected.
Deep copies cannot be created, so the cached objects are done using a best effort copy.
The pytest collection cache wasn't being copied from, resulting in the cached objects being inadvertently modified more than expected. This would manifest as strange errors when you ran something a third time or later, typically from fixture value reuse, and only on tests that had fixtures that were affected.
Deep copies cannot be created, so the cached objects are done using a best effort copy.