chore(deps): update dependency pytest-xdist to v3.8.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pytest-xdist (changelog)	3.3.1 → 3.8.0

---

Release Notes

pytest-dev/pytest-xdist (pytest-xdist)

v3.8.0

Compare Source

===============================

Features

• #&#8203;1083 <https://github.com/pytest-dev/pytest-xdist/issues/1083>_: Add --no-loadscope-reorder and --loadscope-reorder option to control whether to automatically reorder tests in loadscope for tests where relative ordering matters. This only applies when using loadscope.

  For example, [test_file_1, test_file_2, ..., test_file_n] are given as input test files, if --no-loadscope-reorder is used, for either worker, the test_file_a will be executed before test_file_b only if a < b.

  The default behavior is to reorder the tests to maximize the number of tests that can be executed in parallel.

v3.7.0

Compare Source

===============================

Features

• #&#8203;1142 <https://github.com/pytest-dev/pytest-xdist/issues/1142>_: Added support for Python 3.13.

• #&#8203;1144 <https://github.com/pytest-dev/pytest-xdist/issues/1144>_: The internal steal command is now atomic - it unschedules either all requested tests or none.

  This is a prerequisite for group/scope support in the worksteal scheduler, so test groups won't be broken up incorrectly.

• #&#8203;1170 <https://github.com/pytest-dev/pytest-xdist/issues/1170>_: Add the --px arg to create proxy gateways.

  Proxy gateways are passed to additional gateways using the via keyword.
  They can serve as a way to run multiple workers on remote machines.

• #&#8203;1200 <https://github.com/pytest-dev/pytest-xdist/issues/1200>_: Now multiple xdist_group markers are considered when assigning tests to groups (order does not matter).

  Previously, only the last marker would assign a test to a group, but now if a test has multiple xdist_group marks applied (for example via parametrization or via fixtures), they are merged to make a new group.

Removals

• #&#8203;1162 <https://github.com/pytest-dev/pytest-xdist/issues/1162>_: Dropped support for EOL Python 3.8.

Trivial Changes

• #&#8203;1092 <https://github.com/pytest-dev/pytest-xdist/issues/1092>_: Update an error message to better indicate where users should go for more information.

• #&#8203;1190 <https://github.com/pytest-dev/pytest-xdist/issues/1190>_: Switched to using a SPDX license identifier introduced in PEP 639.

v3.6.1

Compare Source

===============================

Bug Fixes

• #&#8203;1071 <https://github.com/pytest-dev/pytest-xdist/issues/1071>_: Add backward compatibility for deadlock issue with the execnet new main_thread_only "execmodel" triggered when pytest-cov accesses rinfo.

v3.6.0

Compare Source

===============================

This release was YANKED due to a regression fixed in 3.6.1.

Features

• #&#8203;1027 <https://github.com/pytest-dev/pytest-xdist/pull/1027>_: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 (for example #​620 #​620`__).

Bug Fixes

• #&#8203;1024 <https://github.com/pytest-dev/pytest-xdist/issues/1024>_: 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.

• #&#8203;1028 <https://github.com/pytest-dev/pytest-xdist/issues/1028>_: Fixed compatibility issue between looponfail and editable installs.

• #&#8203;620 <https://github.com/pytest-dev/pytest-xdist/issues/620>_: 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.

• #&#8203;937 <https://github.com/pytest-dev/pytest-xdist/issues/937>_: Fixed a bug where plugin would raise an incompatibility error with --pdb despite using -n0.

Removals

• #&#8203;1053 <https://github.com/pytest-dev/pytest-xdist/issues/1053>_: Dropped support for Python 3.7.

• #&#8203;1057 <https://github.com/pytest-dev/pytest-xdist/issues/1057>_: pytest>=7.0.0 is now required.

  execnet>=2.1.0 is now required.

Trivial Changes

• #&#8203;1020 <https://github.com/pytest-dev/pytest-xdist/issues/1020>_: 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.

• #&#8203;1057 <https://github.com/pytest-dev/pytest-xdist/issues/1057>_: The internals of pytest-xdist are now fully typed. The typing is not exposed yet.

• #&#8203;996 <https://github.com/pytest-dev/pytest-xdist/issues/996>_: Adjusted license file format and content to ensure security scanners will identity the license.

v3.5.0

Compare Source

===============================

Features

• #&#8203;632 <https://github.com/pytest-dev/pytest-xdist/issues/632>_: --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.

v3.4.0

Compare Source

===============================

Features

• #&#8203;963 <https://github.com/pytest-dev/pytest-xdist/issues/963>_: 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.

• #&#8203;965 <https://github.com/pytest-dev/pytest-xdist/issues/965>_: Added support for Python 3.12.

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.