GitHub user pquentin opened a pull request:
https://github.com/apache/libcloud/pull/1170
Fix tests with pytest 3.4
## Fix tests with pytest 3.4
### Description
The 3.4 pytest release introduced a breaking change: pytest no longer
changes log levels: the default log level is now Python's default: WARNING.
This commit ensures the test no longer depends on external log levels.
pytest 3.4 also adds a .pytest_cache folder: ignore it.
### Status
- done, ready for review
### Checklist (tick everything that applies)
- [x] [Code
linting](http://libcloud.readthedocs.org/en/latest/development.html#code-style-guide)
(required, can be done after the PR checks)
- [ ] Documentation
- [x] [Tests](http://libcloud.readthedocs.org/en/latest/testing.html)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pquentin/libcloud paramiko-log-level
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/1170.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1170
----
commit 78f00f97fbc38333cb04ac43ded74f94458708a1
Author: Quentin Pradet <quentinp@...>
Date: 2018-02-02T11:57:27Z
Fix paramiko test with pytest 3.4
The 3.4 pytest release introduced a breaking change: pytest no longer
changes log levels: the default log level is now Python's default:
WARNING. This commit ensures the test no longer depends on external log
levels.
commit fb622acb5da58911e680cfe0f3cfe12ec7d36191
Author: Quentin Pradet <quentinp@...>
Date: 2018-02-02T11:59:42Z
Ignore pytest 3.4 cache directory
----
---