Update pytest-xdist requirement from ~=3.4 to ~=3.5

[dependabot[bot]]

Updates the requirements on pytest-xdist to permit the latest version.

Changelog

Sourced from pytest-xdist's changelog.

pytest-xdist 3.5.0 (2023-11-21)

Features

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

pytest-xdist 3.4.0 (2023-11-11)

Features

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

• [#965](https://github.com/pytest-dev/pytest-xdist/issues/965) <https://github.com/pytest-dev/pytest-xdist/issues/965>_: Added support for Python 3.12.

pytest-xdist 3.3.1 (2023-05-19)

Bug Fixes

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

pytest-xdist 3.3.0 (2023-05-12)

Features

• [#555](https://github.com/pytest-dev/pytest-xdist/issues/555) <https://github.com/pytest-dev/pytest-xdist/issues/555>_: Improved progress output when collecting nodes to be less verbose.

pytest-xdist 3.2.1 (2023-03-12)

Bug Fixes

... (truncated)

Commits

• 95b309e Release 3.5.0
• 3fe877b LoadScope scheduler: Sort scopes by number of tests to assign biggest scopes ...
• f36ea25 Create GitHub release after deploy (#973)
• d81f575 Merge pull request #969 from pytest-dev/pre-commit-ci-update-config
• 1d26164 [pre-commit.ci] pre-commit autoupdate
• 5f43575 Merge pull request #966 from pytest-dev/release-3.4.0
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions[bot]]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-spark contributing guide.

[github-actions[bot]]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-spark contributing guide.