Ran Benita

Gave this another (quick) look. First, the example in the first commit message is not very fitting, because `@pytest.mark.parametrize()` parametrizations are `function` scoped, so they don't get a chance to...

Indeed, we're handling this in #9248.

@aaltat Thanks for the detailed report! We are seeing something similar in pytest CI, which may or may not be related. What I'd be interested in finding out first is...

This looks like a crash in native code. The `pywinauto` is doing some invalid COM (Windows RPC) calls in `uia_element_info.py, line 269 in _get_elements`. I am not sure why the...

@rsyring Does ```py @pytest.fixture(autouse=True, scope='class') @classmethod def prep_class(cls, db): ``` not work?

The `@final` annotations are really just a way to say "we did not design this class for inheritance, if you inherit from it you're on your own". But it's a...

@FRiMN Can you provide a reproduction? Otherwise it is not very actionable. --- @volans- The problem in your case is that the `logging.basicConfig(level=logging.INFO)` call does nothing. The pytest logging capturing...

> My expectation would be that pytest should not alter the logs generated by the application under test Yes that would have been best, but there are competing desires and...

Thanks for the report, I will take a look when I get a chance. 7.1 had some internal conftest refactorings. If you manage to provide a reproduction that'd be great.

> Why a comment rather than a "needs backport" label? I don't have a preference really, it was easier to copy from release-on-comment but can probably be changed if we...