%global _empty_manifest_terminate_build 0 Name: python-nose-parallel Version: 0.4.0 Release: 1 Summary: A nosetests plugin to split test suites to run in parallel License: MIT License URL: https://github.com/dlanger/nose-parallel Source0: https://mirrors.nju.edu.cn/pypi/web/packages/70/60/039898d68516d2086db9b8ec8e318f84f44a15a8584b2abdfc2d97980a68/nose-parallel-0.4.0.tar.gz BuildArch: noarch %description A plugin to help split up your tests runs across multiple machines. In an ideal world, test suites should be fast enough that they can be run locally on a single machine without extra engineering. This plugin is there to help when you can't make that to happen. This **won't** help you run tests in parallel on one machine in different threads; that's what the built-in `multiprocess `_ plugin is for. This **will** help you split up your test suites so that you can run the suites on multiple machines and not have the same test run twice - think Jenkins with the `multijob `_ plugin, or CI services like `CircleCI `_. %package -n python3-nose-parallel Summary: A nosetests plugin to split test suites to run in parallel Provides: python-nose-parallel BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-nose-parallel A plugin to help split up your tests runs across multiple machines. In an ideal world, test suites should be fast enough that they can be run locally on a single machine without extra engineering. This plugin is there to help when you can't make that to happen. This **won't** help you run tests in parallel on one machine in different threads; that's what the built-in `multiprocess `_ plugin is for. This **will** help you split up your test suites so that you can run the suites on multiple machines and not have the same test run twice - think Jenkins with the `multijob `_ plugin, or CI services like `CircleCI `_. %package help Summary: Development documents and examples for nose-parallel Provides: python3-nose-parallel-doc %description help A plugin to help split up your tests runs across multiple machines. In an ideal world, test suites should be fast enough that they can be run locally on a single machine without extra engineering. This plugin is there to help when you can't make that to happen. This **won't** help you run tests in parallel on one machine in different threads; that's what the built-in `multiprocess `_ plugin is for. This **will** help you split up your test suites so that you can run the suites on multiple machines and not have the same test run twice - think Jenkins with the `multijob `_ plugin, or CI services like `CircleCI `_. %prep %autosetup -n nose-parallel-0.4.0 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-nose-parallel -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Sun Apr 23 2023 Python_Bot - 0.4.0-1 - Package Spec generated