Closed swt2c closed 2 years ago
Okay, I figured out why I was only seeing this on the Fedora builders: the builders had been upgraded to pytest-3.1.1, but pytest-3.0.7 was the latest version pushed out to the mirrors. Now that pytest-3.1.1 has been pushed to the mirrors, I can reproduce this error locally. I did a bit more investigation and tried pytest-3.1.0 - the same failure occurs there as well.
Thus, it seems that this failure started with pytest-3.1.0. I am not familiar enough with the code though to figure out why it fails, though.
I inadvertently experienced this as well while working on a separate issue. If I remember correctly there were some recent changes in pytest with regard to "setup" and gathering tests.
We've been wanting to upgrade to pytest 3.1.3 but encountered this bug as well. What is the recommendation? Can these failing tests be ignored? Should we stick with pytest 3.0.x?
They are isolated to "loop on failing" AFAICT, so unless you use that feature you should not have problems related to it. I have been using 3.1
at work and the latest xdist at work without issues.
I'm seeing a test failure which unfortunately only seems to happen when I run on the Fedora build machines (it does not happen when I build locally). Has anyone seen this before? If not, I'll keep digging into it.