test: Use @pytest.mark.flaky instead of @flaky.flaky
#2911
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use the more modern `@pytest.mark.flaky` decorator to mark tests as flaky, rather than `@flaky.flaky`. This avoids type checking issues, and improves compatibility with other implementations of the marker, such as `pytest-rerunfailures`. Signed-off-by: Michał Górny <mgorny@gentoo.org>
gaborbernat
approved these changes
Jul 26, 2025
|
Thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the more modern
@pytest.mark.flakydecorator to mark tests as flaky, rather than@flaky.flaky. This avoids type checking issues, and improves compatibility with other implementations of the marker, such aspytest-rerunfailures.Thanks for contributing, make sure you address all the checklists (for details on how see development documentation)
tox -e fix)docs/changelogfolderI think this doesn't justify a news item, since it won't affect end users — but I can write one if you wish.