Source: aiorwlock
Version: 0.6.0-2
Severity: important
User: [email protected]
Usertags: pytest-v6

Hi,

aiorwlock FTBFS with pytest 6 in unstable because it uses a deprecated
feature that will be removed soon, and that, by default, considered an
error in pytest 6.

The top of the error log below has more details.

==================================== ERRORS ====================================
_________________ ERROR collecting tests/test_corner_cases.py __________________
/usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:83: in <lambda>
    self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
../../../tests/conftest.py:45: in pytest_pycollect_makeitem
    item = pytest.Function(name, parent=collector)
/usr/lib/python3/dist-packages/_pytest/nodes.py:95: in __call__
    warnings.warn(NODE_USE_FROM_PARENT.format(name=self.__name__), stacklevel=2)
E   pytest.PytestDeprecationWarning: Direct construction of Function has been 
deprecated, please use Function.from_parent.
E   See 
https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent
 for more details.
____________________ ERROR collecting tests/test_rwlock.py _____________________
/usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python3/dist-packages/pluggy/manager.py:83: in <lambda>
    self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
../../../tests/conftest.py:45: in pytest_pycollect_makeitem
    item = pytest.Function(name, parent=collector)
/usr/lib/python3/dist-packages/_pytest/nodes.py:95: in __call__
    warnings.warn(NODE_USE_FROM_PARENT.format(name=self.__name__), stacklevel=2)
E   pytest.PytestDeprecationWarning: Direct construction of Function has been 
deprecated, please use Function.from_parent.
E   See 
https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent
 for more details.
=============================== warnings summary ===============================
/<<PKGBUILDDIR>>/tests/test_corner_cases.py:25
  /<<PKGBUILDDIR>>/tests/test_corner_cases.py:25: PytestUnknownMarkWarning: 
Unknown pytest.mark.run_loop - is this a typo?  You can register custom marks 
to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_corner_cases.py:40
  /<<PKGBUILDDIR>>/tests/test_corner_cases.py:40: PytestUnknownMarkWarning: 
Unknown pytest.mark.run_loop - is this a typo?  You can register custom marks 
to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_corner_cases.py:69
  /<<PKGBUILDDIR>>/tests/test_corner_cases.py:69: PytestUnknownMarkWarning: 
Unknown pytest.mark.run_loop - is this a typo?  You can register custom marks 
to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_corner_cases.py:107
  /<<PKGBUILDDIR>>/tests/test_corner_cases.py:107: PytestUnknownMarkWarning: 
Unknown pytest.mark.run_loop - is this a typo?  You can register custom marks 
to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:73
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:73: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:93
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:93: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:100
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:100: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:122
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:122: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:146
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:146: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:173
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:173: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:199
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:199: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:225
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:225: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:244
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:244: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:294
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:294: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:340
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:340: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:387
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:387: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:440
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:440: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:448
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:448: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:456
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:456: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:486
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:486: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:495
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:495: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:504
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:504: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

/<<PKGBUILDDIR>>/tests/test_rwlock.py:513
  /<<PKGBUILDDIR>>/tests/test_rwlock.py:513: PytestUnknownMarkWarning: Unknown 
pytest.mark.run_loop - is this a typo?  You can register custom marks to avoid 
this warning - for details, see https://docs.pytest.org/en/stable/mark.html
    @pytest.mark.run_loop

-- Docs: https://docs.pytest.org/en/stable/warnings.html
=========================== short test summary info ============================
ERROR ../../../tests/test_corner_cases.py - pytest.PytestDeprecationWarning: ...
ERROR ../../../tests/test_rwlock.py - pytest.PytestDeprecationWarning: Direct...
!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!!
======================== 23 warnings, 2 errors in 0.09s ========================
E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd 
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_aiorwlock/build; python3.9 -m pytest 
{dir}/tests
dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit 
code 13
make: *** [debian/rules:8: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Reply via email to