pytest-xdist 3.0.2 (2022-10-25)

Bug Fixes

• [#813](https://github.com/pytest-dev/pytest-xdist/issues/813) <https://github.com/pytest-dev/pytest-xdist/issues/813>_: Cancel shutdown when a crashed worker is restarted.

Deprecations

• [#825](https://github.com/pytest-dev/pytest-xdist/issues/825) <https://github.com/pytest-dev/pytest-xdist/issues/825>_: The --rsyncdir command line argument and rsyncdirs config variable are deprecated.

  The rsync feature will be removed in pytest-xdist 4.0.

• [#826](https://github.com/pytest-dev/pytest-xdist/issues/826) <https://github.com/pytest-dev/pytest-xdist/issues/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](https://github.com/pytest-dev/pytest-xdist/issues/791) <https://github.com/pytest-dev/pytest-xdist/issues/791>_: Document the pytest_xdist_auto_num_workers hook.

• [#796](https://github.com/pytest-dev/pytest-xdist/issues/796) <https://github.com/pytest-dev/pytest-xdist/issues/796>_: Added known limitations section to documentation.

• [#829](https://github.com/pytest-dev/pytest-xdist/issues/829) <https://github.com/pytest-dev/pytest-xdist/issues/829>_: Document the -n logical option.

Features

• [#792](https://github.com/pytest-dev/pytest-xdist/issues/792) <https://github.com/pytest-dev/pytest-xdist/issues/792>_: The environment variable PYTEST_XDIST_AUTO_NUM_WORKERS can now be used to specify the default for -n auto and -n logical.

• [#812](https://github.com/pytest-dev/pytest-xdist/issues/812) <https://github.com/pytest-dev/pytest-xdist/issues/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