|
|
|
|
Changelog for python312-pytest-xdist-3.5.0-1.5.noarch.rpm :
* Mon Nov 27 2023 Dirk Müller - update to 3.5.0: * ``--dist=loadscope`` now sorts scopes by number of tests to assign largest scopes early -- in many cases this should improve overall test session running time, as there is less chance of a large scope being left to be processed near the end of the session, leaving other workers idle. * Thu Nov 16 2023 Benoît Monin - update to 3.4.0: * #963: Wait for workers to finish reporting when test run stops early. * #965: Added support for Python 3.12. * Mon May 22 2023 Dirk Müller - update to 3.3.1: * Avoid remote calls during startup as execnet by default does not ensure remote affinity with the main thread and might accidentally schedule the pytest worker into a non-main thread, which breaks numerous frameworks, for example ``asyncio``, ``anyio``, ``PyQt/PySide``, etc. A more safe correction will require thread affinity in ``execnet`` * Sun May 14 2023 Dirk Müller - update to 3.3.0: * Improved progress output when collecting nodes to be less verbose. * Fri Apr 21 2023 Dirk Müller - add sle15_python_module_pythons (jsc#PED-68) * Thu Apr 13 2023 Matej Cepl - Make calling of %{sle15modernpython} optional. * Mon Mar 27 2023 Dirk Müller - update to 3.2.1: * Fixed hang in ``worksteal`` scheduler. * Improved Documentation * Document limitations for debugging due to standard I/O of workers not being forwarded. Also, mention remote debugging as a possible workaround. Features: * Users can now configure ``load`` scheduling precision using ``--maxschedchunk`` command line option. * New ``worksteal`` scheduler, based on the idea of `work stealing It\'s similar to ``load`` scheduler, but it should handle tests with significantly differing duration better, and, at the same time, it should provide similar or better reuse of fixtures. * Wed Nov 30 2022 Daniel Garcia - Remove python_module macro definition- Use autosetup instead of setup + autopatch- Remove reintroduce-slave-terminology.patch- Remove 0001-Revert-Remove-compat-for-pytest-6.patch- Update to 3.0.2: [#] Bug Fixes * #813: Cancel shutdown when a crashed worker is restarted. [#] Deprecations * #825: The --rsyncdir command line argument and rsyncdirs config variable are deprecated. * The rsync feature will be removed in pytest-xdist 4.0. * #826: The --looponfail command line argument and looponfailroots config variable are deprecated. * The loop-on-fail feature will be removed in pytest-xdist 4.0. [#] Improved Documentation * #791: Document the pytest_xdist_auto_num_workers hook. * #796: Added known limitations section to documentation. * #829: Document the -n logical option. [#] Features * #792: The environment variable PYTEST_XDIST_AUTO_NUM_WORKERS can now be used to specify the default for -n auto and -n logical. * #812: Partially restore old initial batch distribution algorithm in LoadScheduling. * pytest orders tests for optimal sequential execution - i. e. avoiding unnecessary setup and teardown of fixtures. So executing tests in consecutive chunks is important for optimal performance. * In v1.14, initial test distribution in LoadScheduling was changed to round-robin, optimized for the corner case, when the number of tests is less than 2 * number of nodes. At the same time, it became worse for all other cases. * For example: if some tests use some \"heavy\" fixture, and these tests fit into the initial batch, with round-robin distribution the fixture will be created min(n_tests, n_workers) times, no matter how many other tests there are. * With the old algorithm (before v1.14), if there are enough tests not using the fixture, the fixture was created only once. * So restore the old behavior for typical cases where the number of tests is much greater than the number of workers (or, strictly speaking, when there are at least 2 tests for every node). [#] Removals * #468: The --boxed command-line option has been removed. If you still need this functionality, install pytest-forked separately. [#] Trivial Changes * #468: The py dependency has been dropped. * #822: Replace internal usage of py.log with a custom solution (but with the same interface). * #823: Remove usage of py._pydir as an rsync candidate. * #824: Replace internal usages of py.path.local by pathlib.Path. * Sat Jan 15 2022 Matthias Fehring - Update to 2.5.0 * Features + Full compatibility with pytest 7 - no deprecation warnings or use of legacy features. + New --dist=loadgroup option, which ensures all tests marked with AATTpytest.mark.xdist_group run in the same session/worker. Other tests run distributed as in --dist=load. * Trivial Changes + Use AATTpytest.hookspec decorator to declare hook options in newhooks.py to avoid warnings in pytest 7.0. + Use up-to-date setup.cfg/pyproject.toml packaging setup. + Started using type annotations and mypy checking internally. The types are incomplete and not published.- Changes from 2.4.0 * Features + On Linux, the process title now changes to indicate the current worker state (running/idle). Depends on the setproctitle package, which can be installed with pip install pytest-xdist[setproctitle]. + Add support for Python 3.10.- Changes from 2.3.0 * Deprecations and Removals + Python 3.5 is no longer supported. * Features + Add --numprocesses=logical flag, which automatically uses the number of logical CPUs available, instead of physical CPUs with auto. This is very useful for test suites which are not CPU-bound. + Added new pytest_handlecrashitem hook to allow handling and rescheduling crashed items. * Bug Fixes + Copy the parent process sys.path into local workers, to work around execnet\'s python -c adding the current directory to sys.path. + Fix issue caused by changing the branch name of the pytest repository. * Trivial Changes + Replace master with controller where ever possible. + Use \'main\' to refer to pytest default branch in tox env names.- Update patches * reintroduce-slave-terminology.patch * 0001-Revert-Remove-compat-for-pytest-6.patch- Require setuptools_scm >= 6.0 for building * Tue Feb 02 2021 Dirk Müller - update to 2.2.0: * Internal errors in workers are now propagated to the master node.
|
|
|