Created attachment 1573892 [details] Full log from Copr python-APScheduler 3.5.3-4.fc31 fails to build with pytest 4: ==================================== ERRORS ==================================== _____________________ ERROR collecting tests/test_util.py ______________________ /usr/lib/python3.8/site-packages/pluggy/hooks.py:296: in __call__ return self._hookexec(self, self.get_hookimpls(), kwargs) /usr/lib/python3.8/site-packages/pluggy/manager.py:68: in _hookexec return self._inner_hookexec(hook, methods, kwargs) /usr/lib/python3.8/site-packages/pluggy/manager.py:59: in <lambda> self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall( /usr/lib/python3.8/site-packages/_pytest/python.py:238: in pytest_pycollect_makeitem res = list(collector._genfunctions(name, obj)) /usr/lib/python3.8/site-packages/_pytest/python.py:414: in _genfunctions self.ihook.pytest_generate_tests(metafunc=metafunc) /usr/lib/python3.8/site-packages/pluggy/hooks.py:296: in __call__ return self._hookexec(self, self.get_hookimpls(), kwargs) /usr/lib/python3.8/site-packages/pluggy/manager.py:68: in _hookexec return self._inner_hookexec(hook, methods, kwargs) /usr/lib/python3.8/site-packages/pluggy/manager.py:59: in <lambda> self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall( /usr/lib/python3.8/site-packages/_pytest/python.py:141: in pytest_generate_tests metafunc.parametrize(*marker.args, **marker.kwargs) /usr/lib/python3.8/site-packages/_pytest/python.py:1001: in parametrize argnames, parameters = ParameterSet._for_parametrize( /usr/lib/python3.8/site-packages/_pytest/mark/structures.py:119: in _for_parametrize if len(param.values) != len(argnames): E TypeError: object of type 'MarkDecorator' has no len() =============================== warnings summary =============================== This blocks the Python 3.8 rebuild but it is not Python 3.8 specific.
Please respond.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
The coordinated rebuild of Python 3.8 has started in the `f32-python` side tag. If you figure out how to rebuild this package, please don't rebuild it in regular rawhide, but use the side tag instead: on branch master: $ fedpkg build --target=f32-python To wait for a build to show up in the side tag, do: $ koji wait-repo f32-python --build=<nvr> Where <nvr> is name-version-release of the source package, e.g. python-foo-1.1-2.fc32. An updated mock config is posted at: http://copr.fedorainfracloud.org/coprs/g/python/python3.8/ Note that it will take a while before the essential packages are rebuilt, so don't expect all your dependencies to be available right away. Thanks. Let us know if you need up to date info, or if you have any questions. PS this message is mass posted to all the bugs that block the PYTHON38 bug. If this is also a Fedora 31 FTBFS bug and you manage to fix it, you can do a f31 build as usual: on branch f31: $ fedpkg build
The f32-python side tag has been merged. In order to rebuild the package, do it in regular rawhide, but please wait until python3-3.8 is tagged: $ koji wait-repo f32-build --build python3-3.8.0~b3-3.fc32 If your built already started in f32-python, after it is finished, please tag it to rawhide with: $ koji tag-build f32-pending <nvr> For example: $ koji tag-build f32-pending libreoffice-6.3.0.4-3.fc32 Thanks! (This comment is mass posted to all bugzillas blocking the PYTHON38 tracking bug.)
(Python 3.8 has landed in the rawhide buildroot.)
Dear Maintainer, your package has not been built successfully in 31. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package can be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages which still have open FTBFS bugs from Fedora 31 will be retired. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule
The package was retired after being orphaned for 6+ weeks. Leaving this open for Fedora 31.
Dear Maintainer, your package has not been built successfully in 31. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages not successfully rebuilt at least on 30 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule
Dear Maintainer, your package has not been built successfully in 31. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. Following the latest policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks. A week before the mass branching of Fedora 32 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 30 will be retired regardless of the status of this bug. [1] https://fedoraproject.org/wiki/Updates_Policy [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedoraproject.org/wiki/Releases/32/Schedule
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
FEDORA-2020-9aabc60c36 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9aabc60c36
First time I had to go over a stable update. Not sure I did it right. Here is the koji build https://koji.fedoraproject.org/koji/buildinfo?buildID=1524171 And here is the bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9aabc60c36
FEDORA-2020-9aabc60c36 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-9aabc60c36` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9aabc60c36 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-9aabc60c36 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days