🧪 Stop using pytest-forked
#703
Merged
+22
−15
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
This plugin is incompatible with Pytest 7+, it's difficult to fix upstream and there is no timeline for addressing that. The patch also bumps the top version boundary of Pytest to 7.2 due to the pinned `pytest-cov` raising warnings. Fixes cherrypy#502 Resolves cherrypy#511 Closes cherrypy#680 Resolves cherrypy#681
This also links several related issues.
webknjaz
force-pushed
the
maintenance/unfork-pytest
branch
from
b9a1e28 to
32e09b4
Compare
Member
Author
|
FTR, somebody found that a workaround would be reordering the tests so that forked ones aren't last in the test modules: aio-libs/aiohttp-devtools#505 (comment). I think I originally found this hint in some Fedora downstream discussions. |
Member
Author
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.
This plugin is incompatible with Pytest 7+, it's difficult to fix upstream and there is no timeline for addressing that.
The patch also bumps the top version boundary of Pytest to 7.2 due to the pinned
pytest-covraising warnings.Fixes #502
Resolves #511
Closes #680
Resolves #681
❓ What kind of change does this PR introduce?
This change is