So the patch won't fully fix the issue for pytest-rerunfailures, but since the pytest upstream bug [1] that this patch fixes was originally posted due to a regression in pytest-rerunfailures I think this is a net improvement.
After applying the fix for [1], the error now in pytest-rerunfailures is that non-function teardown fixtures (e.g. class, module, etc.) do not get called correctly. This was previously a problem that upstream tried to solve in [2] but I think pytest 8.2 introduced changes that cause it to regress again. There is an upstream (rerunfailures) bug [3] to track the issue there. [1] https://github.com/pytest-dev/pytest/issues/12424 [2] https://github.com/pytest-dev/pytest-rerunfailures/commit/0ab54f00d68bb4feadae58d2f4e30f6663495571 [3] https://github.com/pytest-dev/pytest-rerunfailures/issues/267 ** Bug watch added: github.com/pytest-dev/pytest/issues #12424 https://github.com/pytest-dev/pytest/issues/12424 ** Bug watch added: github.com/pytest-dev/pytest-rerunfailures/issues #267 https://github.com/pytest-dev/pytest-rerunfailures/issues/267 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068642 Title: python-flaky/3.8.1-2 and pytest-rerunfailures/12.0-1 vs pytest/8.2.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pytest/+bug/2068642/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
