Up to [cvs.NetBSD.org] / pkgsrc / devel / py-test-xdist
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
py-test-xdist: updated to 3.6.1 pytest-xdist 3.6.1 (2024-04-28) =============================== Bug Fixes --------- - Add backward compatibility for deadlock issue with the ``execnet`` new ``main_thread_only`` "execmodel" triggered when pytest-cov accesses rinfo. pytest-xdist 3.6.0 (2024-04-19) =============================== This release was YANKED due to a regression fixed in 3.6.1. Features -------- - ``pytest-xdist`` workers now always execute the tests in the main thread. Previously some tests might end up executing in a separate thread other than ``main`` in the workers, due to some internal `execnet`` details. This can cause problems specially with async frameworks where the event loop is running in the ``main`` thread. Bug Fixes --------- - Added proper handling of ``shouldstop`` (such as set by ``--max-fail``) and ``shouldfail`` conditions in workers. Previously, a worker might have continued executing further tests before the controller could terminate the session. - Fixed compatibility issue between `looponfail` and editable installs. - Use the new ``main_thread_only`` ``execnet`` "execmodel" so that code which expects to only run in the main thread will now work as expected. - Fixed a bug where plugin would raise an incompatibility error with ``--pdb`` despite using ``-n0``. Removals -------- - Dropped support for Python 3.7. - pytest>=7.0.0 is now required. execnet>=2.1.0 is now required. Trivial Changes --------------- - pytest-xdist's ``setup.py`` file is removed. If you relied on this file, e.g. to install pytest using ``setup.py install``, please see `Why you shouldn't invoke setup.py directly <https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html#summary>`_ for alternatives. - The internals of pytest-xdist are now fully typed. The typing is not exposed yet. - Adjusted license file format and content to ensure security scanners will identity the license.
py-test-xdist: updated to 3.5.0 pytest-xdist 3.5.0 (2023-11-21) Features - ``--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.
py-test-xdist: updated to 3.4.0 pytest-xdist 3.4.0 (2023-11-11) Features - Wait for workers to finish reporting when test run stops early. This makes sure that the results of in-progress tests are displayed. Previously these reports were being discarded, losing information about the test run. - Added support for Python 3.12.
py-test-xdist: updated to 3.3.1 pytest-xdist 3.3.1 (2023-05-19) Bug Fixes - 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`` pytest-xdist 3.3.0 (2023-05-12) Features - Improved progress output when collecting nodes to be less verbose.
py-test-xdist: updated to 3.2.1 pytest-xdist 3.2.1 Fixed hang in ``worksteal`` scheduler.
py-test-xdist: updated to 3.2.0 pytest-xdist 3.2.0 (2023-02-07) 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. Trivial Changes Make the tests pass even when $PYTEST_XDIST_AUTO_NUM_WORKERS is set.
py-test-xdist: updated to 3.1.0 pytest-xdist 3.1.0 (2022-12-01) =============================== Features -------- - Users can now set a default distribution mode in their configuration file: .. code-block:: ini [pytest] addopts = --dist loadscope - Python 3.11 is now officially supported. Removals -------- - Python 3.6 is no longer supported.
py-test-xdist: updated to 3.0.2 pytest-xdist 3.0.2 (2022-10-25) =============================== Bug Fixes --------- - Cancel shutdown when a crashed worker is restarted. Deprecations ------------ - The ``--rsyncdir`` command line argument and ``rsyncdirs`` config variable are deprecated. The rsync feature will be removed in pytest-xdist 4.0. - 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 ---------------------- - Document the ``pytest_xdist_auto_num_workers`` hook. - Added known limitations section to documentation. - Document the ``-n logical`` option. Features -------- - The environment variable ``PYTEST_XDIST_AUTO_NUM_WORKERS`` can now be used to specify the default for ``-n auto`` and ``-n logical``. - 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 -------- - The ``--boxed`` command-line option has been removed. If you still need this functionality, install `pytest-forked <https://pypi.org/project/pytest-forked>`__ separately. Trivial Changes --------------- - The ``py`` dependency has been dropped. - Replace internal usage of ``py.log`` with a custom solution (but with the same interface). - Remove usage of ``py._pydir`` as an rsync candidate. - Replace internal usages of ``py.path.local`` by ``pathlib.Path``.
py-test-xdist: update to 2.5.0. pytest-xdist 2.5.0 (2021-12-10) =============================== Features -------- - `#722 `_: Full compatibility with pytest 7 - no deprecation warnings or use of legacy features. - `#733 `_: New ``--dist=loadgroup`` option, which ensures all tests marked with ``@pytest.mark.xdist_group`` run in the same session/worker. Other tests run distributed as in ``--dist=load``. Trivial Changes --------------- - `#708 `_: Use ``@pytest.hookspec`` decorator to declare hook options in ``newhooks.py`` to avoid warnings in ``pytest 7.0``. - `#719 `_: Use up-to-date ``setup.cfg``/``pyproject.toml`` packaging setup. - `#720 `_: Require pytest>=6.2.0. - `#721 `_: Started using type annotations and mypy checking internally. The types are incomplete and not published. pytest-xdist 2.4.0 (2021-09-20) =============================== Features -------- - `#696 `_: 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]``. - `#704 `_: Add support for Python 3.10. pytest-xdist 2.3.0 (2021-06-16) =============================== Deprecations and Removals ------------------------- - `#654 `_: Python 3.5 is no longer supported. Features -------- - `#646 `_: 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. - `#650 `_: Added new ``pytest_handlecrashitem`` hook to allow handling and rescheduling crashed items. Bug Fixes --------- - `#421 `_: Copy the parent process sys.path into local workers, to work around execnet's python -c adding the current directory to sys.path. - `#638 `_: Fix issue caused by changing the branch name of the pytest repository. Trivial Changes --------------- - `#592 `_: Replace master with controller where ever possible. - `#643 `_: Use 'main' to refer to pytest default branch in tox env names. pytest-xdist 2.2.1 (2021-02-09) =============================== Bug Fixes --------- - `#623 `_: Gracefully handle the pending deprecation of Node.fspath by using config.rootpath for topdir. pytest-xdist 2.2.0 (2020-12-14) =============================== Features -------- - `#608 `_: Internal errors in workers are now propagated to the master node. pytest-xdist 2.1.0 (2020-08-25) =============================== Features -------- - `#585 `_: New ``pytest_xdist_auto_num_workers`` hook can be implemented by plugins or ``conftest.py`` files to control the number of workers when ``--numprocesses=auto`` is given in the command-line. Trivial Changes --------------- - `#585 `_: ``psutil`` has proven to make ``pytest-xdist`` installation in certain platforms and containers problematic, so to use it for automatic number of CPUs detection users need to install the ``psutil`` extra:: pip install pytest-xdist[psutil] pytest-xdist 2.0.0 (2020-08-12) =============================== Deprecations and Removals ------------------------- - `#541 `_: Drop backward-compatibility "slave" aliases related to worker nodes. We deliberately moved away from this terminology years ago, and it seems like the right time to finish the deprecation and removal process. - `#569 `_: ``pytest-xdist`` no longer supports Python 2.7. Features -------- - `#504 `_: New functions ``xdist.is_xdist_worker``, ``xdist.is_xdist_master``, ``xdist.get_xdist_worker_id``, to easily identify the current node. Bug Fixes --------- - `#471 `_: Fix issue with Rsync reporting in quiet mode. - `#553 `_: When using ``-n auto``, count the number of physical CPU cores instead of logical ones. Trivial Changes --------------- - `#541 `_: ``pytest-xdist`` now requires ``pytest>=6.0``.
*: remove workaround patches for python 3.6
archivers: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes Could not be committed due to merge conflict: devel/py-traitlets/distinfo The following distfiles were unfetchable (note: some may be only fetched conditionally): ./devel/pvs/distinfo pvs-3.2-solaris.tgz ./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip
devel: Remove SHA1 hashes for distfiles
Fix Python 3.6 build
py-test-xdist: updated to 1.34.0 pytest-xdist 1.34.0 =================== Features -------- - Make ``--pdb`` imply ``--dist no``, as the two options cannot really work together at the moment. Bug Fixes --------- - Fix regression with duplicated arguments via $PYTEST_ADDOPTS in 1.30.0. - Fix ``rsyncdirs`` usage with pytest 6.0. - Do not trigger the deprecated ``pytest_warning_captured`` in pytest 6.0+.
py-test-xdist: updated to 1.33.0 pytest-xdist 1.33.0 Features - Fix warnings support for upcoming pytest 6.0. Trivial Changes - SCM and CI files are no longer included in the source distribution.
py-test-xdist: updated to 1.32.0 pytest-xdist 1.32.0 Deprecations and Removals - Drop support for EOL Python 3.4. Features - Add `testrun_uid` fixture. This is a shared value that uniquely identifies a test run among all workers. This also adds a `PYTEST_XDIST_TESTRUNUID` environment variable that is accessible within a test as well as a command line option `--testrunuid` to manually set the value from outside.
py-test-xdist: updated to 1.31.0 pytest-xdist 1.31.0: Features - Add support for Python 3.8. Bug Fixes - Fix regression that caused custom plugin command-line arguments to be discarded when using ``--tx`` mode.
py-test-xdist: updated to 1.30.0 pytest-xdist 1.30.0: Features * Initialization between workers and master nodes is now more consistent, which fixes a number of long-standing issues related to startup with the -c option. Issues: * Poor interaction between -n# and -c X.cfg * pytest-xdist is not reporting the same nodeid as pytest does This however only works with pytest 5.1 or later, as it required changes in pytest itself.
py-test-xdist: updated to 1.29.0 pytest-xdist 1.29.0: Features - --max-worker-restart now assumes a more reasonable value (4 times the number of nodes) when not given explicitly. This prevents test suites from running forever when the suite crashes during collection. - When the test session is interrupted due to running out of workers, the reason is shown in the test summary for easier viewing. - Compatibility fix for upcoming pytest 5.0: session.exitstatus is now an IntEnum object. Bug Fixes - No longer show an internal error when we run out of workers due to crashes.
py-test-xdist: updated to 1.28.0 pytest-xdist 1.28.0: Features - pytest-xdist now uses the new pytest_report_to_serializable and pytest_report_from_serializable hooks from pytest 4.4 (still experimental). This will make report serialization more reliable and extensible.
py-test-xdist: updated to 1.27.0 pytest-xdist 1.27.0: Features - The new pytest_xdist_getremotemodule hook allows overriding the module run on remote nodes. - Improve behavior of --numprocesses=auto to work well with --pdb option.
py-test-xdist: updated to 1.26.1 pytest-xdist 1.26.1: Bug Fixes Do not implement deprecated pytest_logwarning hook in pytest versions where it is deprecated.
py-test-xdist: updated to 1.26.0 pytest-xdist 1.26.0: Features - The current directory is no longer added ``sys.path`` for local workers, only for remote connections. This behavior is surprising because it makes xdist runs and non-xdist runs to potentially behave differently. Bug Fixes - Warning attributes are checked to make sure they can be dumped prior to serializing the warning for submission to the master node.
py-test-xdist: updated to 1.25.0 pytest-xdist 1.25. Deprecations and Removals Pytest versions older than 3.6 are no longer supported. Features Node setup information is hidden when pytest is run in quiet mode to reduce noise on many-core machines. mainargv is made available in workerinput from the host's sys.argv. This can be used via request.config.workerinput["mainargv"]. Bug Fixes Fix report of module-level skips (pytest.skip(reason, allow_module_level=True)). Fix support for gevent monkeypatching pytest 4.1 support: ExceptionInfo API changes. pytest 4.1 support: pytest_logwarning hook removed.
py-test-xdist: updated to 1.24.1 pytest-xdist 1.24.1: Bug Fixes - Correctly handle warnings created with arguments that can't be serialized during the transfer from workers to master node.
py-test-xdist: updated to 1.24.0 pytest-xdist 1.24.0: Features - New --maxprocesses command-line option that limits the maximum number of workers when using --numprocesses=auto. Bug Fixes - Fix scheduling deadlock in case of inter-test locking.
py-test-xdist: updated to 1.23.2 pytest-xdist 1.23.2: Bug Fixes - Fix issue where Warnings could cause pytest to fail if they do not set the args attribute correctly. pytest-xdist 1.23.1: Bug Fixes - Fix warnings transfer between workers and master node with pytest >= 3.8.py-test-xdist: updated to 1.23.2
py-test-xdist: updated to 1.23.0 1.23.0: Improve collection performance by reducing the number of events sent to master node.
py-test-xdist: updated to 1.22.5 pytest-xdist 1.22.5: Bug Fixes - Revert change that dropped support for pytest<3.4 and require six. This change caused problems in some installations, and was a mistaken in the first place as we should not change version requirements in bug-fix releases unless they fix an actual bug. pytest-xdist 1.22.4: Bug Fixes - Remove last references to obsolete py.code. Remove some unnecessary references to py.builtin. - Workaround cpu detection on Travis CI.
py-test-xdist: updated to 1.22.3 pytest-xdist 1.22.3: Bug Fixes Fix issue of virtualized or containerized environments not reporting the number of CPUs correctly. Trivial Changes Make all classes subclass from object and fix super() call in LoadFileScheduling.
py-test-xdist: updated to 1.22.2 1.22.2: Add backward compatibility for slaveoutput attribute to WorkerController instances.
py-test-xdist: updated to 1.22.1 pytest-xdist 1.22.1 Bug Fixes Fix issue when using loadscope or loadfile where tests would fail to start if the first scope had only one test. Trivial Changes Change terminology used by pytest-xdist to master and worker in arguments and messages (for example --max-worker-reset).
py-test-xdist: updated to 1.22.0 pytest-xdist 1.22.0: Features -------- - Add support for the ``pytest_runtest_logfinish`` hook which will be released in pytest 3.4
py-test-xdist: updated to 1.21.0 pytest-xdist 1.21.0: Deprecations and Removals Drop support for EOL Python 2.6. Features New --dist=loadfile option which load-distributes test to workers grouped by the file the tests live in. Bug Fixes Fix accidental mutation of test report during serialization causing longrepr string-ification to break.
py-test-xdist: update to 1.20.1 1.20.1: Bug Fixes - Fix hang when all worker nodes crash and restart limit is reached - Fix issue where the -n option would still run distributed tests when pytest was run with the --collect-only option
1.20.0: Features - ``xdist`` now supports tests to log results multiple times, improving integration with plugins which require it like `pytest-rerunfailures <https://github.com/gocept/pytest-rerunfailures>_` and `flaky <https://pypi.python.org/pypi/flaky>`_. Bug Fixes - Fix issue where tests were being incorrectly identified if a worker crashed during the ``teardown`` stage of the test.
Updated py-test-xdist to 1.19.1. pytest-xdist 1.19.1 (2017-08-10) ================================ Bug Fixes --------- - Fix crash when transferring internal pytest warnings from workers to the master node. (`#214 <https://github.com/pytest-dev/pytest- xdist/issues/214>`_) pytest-xdist 1.19.0 (2017-08-09) ================================ Deprecations and Removals ------------------------- - ``--boxed`` functionality has been moved to a separate plugin, `pytest-forked <https://github.com/pytest-dev/pytest-forked>`_. This release now depends on `` pytest-forked`` and provides ``--boxed`` as a backward compatibility option. (`#1 <https://github.com/pytest-dev/pytest-xdist/issues/1>`_) Features -------- - New ``--dist=loadscope`` option: sends group of related tests to the same worker. Tests are grouped by module for test functions and by class for test methods. See ``README.rst`` for more information. (`#191 <https://github.com /pytest-dev/pytest-xdist/issues/191>`_) - Warnings are now properly transferred from workers to the master node. (`#92 <https://github.com/pytest-dev/pytest-xdist/issues/92>`_) Bug Fixes --------- - Fix serialization of native tracebacks (``--tb=native``). (`#196 <https://github.com/pytest-dev/pytest-xdist/issues/196>`_)
pytest-xdist 1.18.2: Bug Fixes - Removal of unnecessary dependency on incorrect version of py. - Fix bug in internal event-loop error handler in the master node. This bug would shadow the original errors making extremely hard/impossible for users to diagnose the problem properly
1.18.1: Bug Fixes - Fixed serialization of ``longrepr.sections`` during error reporting from workers. - Fix ``ReprLocal`` not being unserialized breaking --showlocals usages.
The pytest-xdist plugin extends py.test with some unique test execution modes: * test run parallelization: if you have multiple CPUs or hosts you can use those for a combined test run. This allows to speed up development or to use special resources of remote machines. * --boxed: (not available on Windows) run each test in a boxed subprocess to survive SEGFAULTS or otherwise dying processes * --looponfail: run your tests repeatedly in a subprocess. After each run py.test waits until a file in your project changes and then re-runs the previously failing tests. This is repeated until all tests pass after which again a full run is performed. * Multi-Platform coverage: you can specify different Python interpreters or different platforms and run tests in parallel on all of them.