Skip to content

[7.4.x] fix #10447 - consider marks in reverse mro order to give base classes priority #11545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 24, 2023

Conversation

github-actions[bot]
Copy link
Contributor

Backport of PR #11155 to 7.4.x branch. PR created by backport workflow.

@nicoddemus nicoddemus closed this Oct 24, 2023
@nicoddemus nicoddemus reopened this Oct 24, 2023
@nicoddemus nicoddemus enabled auto-merge (squash) October 24, 2023 14:44
@nicoddemus nicoddemus merged commit 44ad1c9 into 7.4.x Oct 24, 2023
@nicoddemus nicoddemus deleted the backport-11155-to-7.4.x branch October 24, 2023 15:04
cas-- added a commit to cas--/Deluge that referenced this pull request Feb 18, 2025
The Console UI tests started stalling after the realese of pytest 7.4.3
which was a result of the reversing the mro order of fixtures on
classes, to give base classes priority.

The change resulted in `base_fixture` being sorted before `client` and
`daemon` fixtures and the tests stalled, likely due to the use of yield
in base_fixture.

    # pytest 7.4.2
    [Mark(name='usefixtures', args=('client', 'daemon'), kwargs={})],
    [Mark(name='usefixtures', args=('base_fixture',), kwargs={})],
    # pytest 7.4.3
    [Mark(name='usefixtures', args=('base_fixture',), kwargs={})],
    [Mark(name='usefixtures', args=('client', 'daemon'), kwargs={})],

The fix is to move base_fixture along with the other fixtures and place it
last.

Refs: pytest-dev/pytest#11545
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants