pytest-3.9.3-3.fc31 FTBFS, Python 2 tests give:

    import unittest.mock as mock
E   ImportError: No module named mock

That is kinda expected as this was added in Python 3. Yet it used to work.



+ /builddir/build/BUILDROOT/pytest-3.9.3-3.fc31.x86_64/usr/bin/pytest-2.7 -r s testing
============================= test session starts ==============================
platform linux2 -- Python 2.7.16, pytest-3.9.3, py-1.7.0, pluggy-0.8.1
hypothesis profile 'default' -> database=DirectoryBasedExampleDatabase('/builddir/build/BUILD/pytest-3.9.3/.hypothesis/examples')
rootdir: /builddir/build/BUILD/pytest-3.9.3, inifile: tox.ini
plugins: hypothesis-4.9.0
collected 2185 items / 2 errors
==================================== ERRORS ====================================
____________________ ERROR collecting testing/test_mark.py _____________________
ImportError while importing test module '/builddir/build/BUILD/pytest-3.9.3/testing/test_mark.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python2.7/site-packages/six.py:709: in exec_
    exec("""exec _code_ in _globs_, _locs_""")
testing/test_mark.py:11: in <module>
    import unittest.mock as mock
E   ImportError: No module named mock
__________________ ERROR collecting testing/code/test_code.py __________________
ImportError while importing test module '/builddir/build/BUILD/pytest-3.9.3/testing/code/test_code.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python2.7/site-packages/six.py:709: in exec_
    exec("""exec _code_ in _globs_, _locs_""")
testing/code/test_code.py:17: in <module>
    import unittest.mock as mock
E   ImportError: No module named mock
!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!
=========================== 2 error in 4.99 seconds ============================



https://apps.fedoraproject.org/koschei/package/pytest

I suspect the update to python2-six 1.11.0-7.fc30.

Fresh scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=33397478 seems to get past the failure, will investigate.