Update pytest to >=6.0.1#4308
Merged
Merged
Conversation
pytest 6.0.0 had issue with `pylint`, complaining for `pytest.mark.*` being `not-callable`.
Codecov Report
@@ Coverage Diff @@
## master #4308 +/- ##
=======================================
Coverage 91.20% 91.20%
=======================================
Files 176 176
Lines 12096 12096
=======================================
Hits 11032 11032
Misses 1064 1064 Continue to review full report at Codecov.
|
Collaborator
Author
|
Snapcraft is getting stuck on travis. Container never starts. Looks like it's unrelated with this PR, merging ... |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
pytest 6.0.0 had issue with
pylint, complaining forpytest.mark.*beingnot-callable. Ref: pytest-dev/pytest#7558pytest6.0.1 has just been released.
❗ I have followed the Contributing to DVC checklist.
📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏