-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Failing test suite with pytest 7 due to deprecation warnings #6663
Comments
These are generally caught automatically by Dependabot PRs (e.g. #6596), so need to report them. Feel free to make a PR to resolve the issue though. |
|
Yep, there are some issues with our Dependabot integration at the moment. But, if it's got an open PR, we should end up looking at it eventually. As mentioned, a PR will help get it updated quickly, if someone else gets to it before a maintainer. |
It's unfortunately not obvious, what was the intention behind your
Hence the detailed report including the analysis. A bot cannot do that for you. |
So, the "misuse" is using it to ensure that no warnings happen? If so, it looks like that is exactly what happened, judging by the commit from several years ago: #2161 If that's the case, then I'm sure we can just delete the lines. We have pytest configured to error on warnings anyway (maybe that wasn't the case when this commit was made). |
Describe the bug
Pytest 7 deprecates the usage of
pytest.warns(None)
. See pytest-dev/pytest#9404 for a discussion about it.The test suite erroring out on any warning fails with pytest 7.1.1
To Reproduce
Expected behavior
Clean pass
Logs/tracebacks
Python Version
aiohttp Version
3.8.1
multidict Version
6.0.2
yarl Version
1.7.2
OS
openSUSE Tumbleweed Linux
Related component
Server, Client
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: