Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency pytest-xdist to v3.6.1 #78

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 11, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pytest-xdist (changelog) 3.3.1 -> 3.6.1 age adoption passing confidence

Release Notes

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

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: Branch creation - "every weekend" in timezone Asia/Tokyo, 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.

@renovate renovate bot changed the title chore(deps): update dependency pytest-xdist to v3.4.0 chore(deps): update dependency pytest-xdist to v3.5.0 Nov 21, 2023
@renovate renovate bot force-pushed the renovate/pytest-xdist-3.x-lockfile branch from 0ecf3c3 to 3691128 Compare November 21, 2023 15:47
@renovate renovate bot force-pushed the renovate/pytest-xdist-3.x-lockfile branch from 3691128 to c36d646 Compare April 19, 2024 21:46
@renovate renovate bot changed the title chore(deps): update dependency pytest-xdist to v3.5.0 chore(deps): update dependency pytest-xdist to v3.6.0 Apr 19, 2024
@renovate renovate bot force-pushed the renovate/pytest-xdist-3.x-lockfile branch from c36d646 to 9700b71 Compare April 20, 2024 06:35
@renovate renovate bot changed the title chore(deps): update dependency pytest-xdist to v3.6.0 chore(deps): update dependency pytest-xdist to v3.5.0 Apr 20, 2024
@renovate renovate bot changed the title chore(deps): update dependency pytest-xdist to v3.5.0 chore(deps): update dependency pytest-xdist to v3.6.1 Apr 28, 2024
@renovate renovate bot force-pushed the renovate/pytest-xdist-3.x-lockfile branch from 9700b71 to 4ed4f51 Compare April 28, 2024 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants