build(deps-dev): bump pytest-xdist from 3.5.0 to 3.6.1
Bumps pytest-xdist from 3.5.0 to 3.6.1.
Changelog
Sourced from pytest-xdist's changelog.
pytest-xdist 3.6.1 (2024-04-28)
Bug Fixes
[#1071](https://github.com/pytest-dev/pytest-xdist/issues/1071) <https://github.com/pytest-dev/pytest-xdist/issues/1071>_: Add backward compatibility for deadlock issue with theexecnetnewmain_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
[#1027](https://github.com/pytest-dev/pytest-xdist/issues/1027) <https://github.com/pytest-dev/pytest-xdist/pull/1027>_:pytest-xdistworkers now always execute the tests in the main thread. Previously some tests might end up executing in a separate thread other thanmainin the workers, due to some internalexecnet`` details. This can cause problems specially with async frameworks where the event loop is running in the ``main`` thread (for example#620 pytest-dev/pytest-xdist#620`__).Bug Fixes
[#1024](https://github.com/pytest-dev/pytest-xdist/issues/1024) <https://github.com/pytest-dev/pytest-xdist/issues/1024>_: Added proper handling ofshouldstop(such as set by--max-fail) andshouldfailconditions in workers. Previously, a worker might have continued executing further tests before the controller could terminate the session.
[#1028](https://github.com/pytest-dev/pytest-xdist/issues/1028) <https://github.com/pytest-dev/pytest-xdist/issues/1028>_: Fixed compatibility issue betweenlooponfailand editable installs.
[#620](https://github.com/pytest-dev/pytest-xdist/issues/620) <https://github.com/pytest-dev/pytest-xdist/issues/620>_: Use the newmain_thread_onlyexecnet"execmodel" so that code which expects to only run in the main thread will now work as expected.
[#937](https://github.com/pytest-dev/pytest-xdist/issues/937) <https://github.com/pytest-dev/pytest-xdist/issues/937>_: Fixed a bug where plugin would raise an incompatibility error with--pdbdespite using-n0.Removals
[#1053](https://github.com/pytest-dev/pytest-xdist/issues/1053) <https://github.com/pytest-dev/pytest-xdist/issues/1053>_: Dropped support for Python 3.7.
[#1057](https://github.com/pytest-dev/pytest-xdist/issues/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
[#1020](https://github.com/pytest-dev/pytest-xdist/issues/1020) <https://github.com/pytest-dev/pytest-xdist/issues/1020>_: pytest-xdist'ssetup.pyfile is removed.If you relied on this file, e.g. to install pytest using
setup.py install, please seeWhy you shouldn't invoke setup.py directly <https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html#summary>_ for alternatives.
... (truncated)
Commits
4dd2978Release 3.6.1b397288Merge pull request #1072 from zmedico/gateway-cache-rinfo12b3cceCache execnet gateway rinfo during WorkerController setupc93a106build(deps): bump hynek/build-and-inspect-python-package (#1066)52e2022[pre-commit.ci] pre-commit autoupdate (#1073)699f939Merge pull request #1070 from pytest-dev/release-3.6.080bc0b8Release 3.6.020e3ac7Use execnet main_thread_only execmodel (#1027)0a4238fMerge pull request #1067 from pytest-dev/pre-commit-ci-update-config0686279[pre-commit.ci] pre-commit autoupdate- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)