Tests on master are failing with pytest 6.1.1

[michael-k]

I've noticed that the baseline tests on master are currently failing. They pass when pytest is pinned to <6.1. Logs are available here:

• fail: https://travis-ci.com/github/michael-k/pytest-django/builds/188604675
• pass: https://travis-ci.com/github/michael-k/pytest-django/builds/188608938

They are failing because '* 1 passed in*' does not match ======================== 1 passed, 2 warnings in 0.05s =========================. The change in the handling of internal warnings in pytest 6.1.0 might be the causing this, but I didn't investigate this further yet (changelog: https://docs.pytest.org/en/stable/changelog.html#improvements).

[bluetech]

Right, looks like the pytest change causes some warnings to appear that were previously hidden, which messes up the matching.

The solution is preferably to fix the warnings, and if not possible, filter (ignore) them.

First warning is

          and: "  /home/travis/build/michael-k/pytest-django/.tox/py38-dj31-postgres-xdist-coverage/lib/python3.8/site-packages/configurations/importer.py:1: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses"

E           and: '    import imp'

which comes from django-configurations. So we should fix it there if possible, but probably filter in the meanwhile.

Second warning is

E           and: '../../../../home/travis/build/michael-k/pytest-django/.tox/py38-dj31-postgres-xdist-coverage/lib/python3.8/site-packages/django/conf/__init__.py:208'

E           and: '  /home/travis/build/michael-k/pytest-django/.tox/py38-dj31-postgres-xdist-coverage/lib/python3.8/site-packages/django/conf/__init__.py:208: RemovedInDjango40Warning: The DEFAULT_HASHING_ALGORITHM transitional setting is deprecated. Support for it and tokens, cookies, sessions, and signatures that use SHA-1 hashing algorithm will be removed in Django 4.0.'

Need to find where it's coming from (not from pytest-django itself at least).

[michael-k]

Need to find where it's coming from (not from pytest-django itself at least).

Might be also coming from django-configurations, see jazzband/django-configurations#263

[michael-k]

I've opened PR jazzband/django-configurations#264 that drops support for Python 2 and should make it possible to switch from imp to importlib, but I haven't figured out how to do that.

[bluetech]

For now I have a fix for this as part of #876 -- just making the tests less sensitive to whether there are warnings are not. I figure we don't want to fail whenever a new one comes up. I also noticed some warnings from mysql libraries.