FIX pytest configuration for v7.1 #300
Merged
Conversation
This file contains 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
|
Merging to get a green CI :) 💚 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current failure is due to a change of behavior with
pytest7.1, from pytest-dev/pytest#9493.This makes it not possible to have twice the same
conftest.pyI found out that we can change this by relying on a plugin, that can be loaded at runtime with option
-pin pytest.this PR implement this as this make it cleaner (we are directly loading the installed configuration as a fixture, not relying on path resolution from pytest that we don't control very well).
Overall, this is cleaner, so hopefully the CI is green tonight.