New LoadScheduling batch distribution logic doesn't work for long-running tests
#855
Comments
|
It looks like using the |
|
Hm... The simplest solution would be to add another scheduler class, derived from LoadScheduling, where initial batch is distributed round-robin. However, it will help only if your slow tests will fit into that initial batch (although if the difference is so huge - looks like previously they did). Another option is to significantly change how LoadScheduling works. I have a few ideas, but not sure how they will turn out in reality. Is the test suite you're talking about publicly available? |
|
Or, maybe, a more flexible solution: limit size of the chunks of consecutive tests that xdist submits to workers (in ini file and/or CLI argument). Setting it to 1 will effectively mean "round-robin distribution". |
|
@amezin Good idea with the config option. My testsuite is public - https://github.com/input-output-hk/cardano-node-tests/tree/master/cardano_node_tests/tests |
amezin
added a commit
to amezin/pytest-xdist
that referenced
this issue
Dec 20, 2022
Maximum number of tests scheduled in one step. Setting it to 1 will force pytest to send tests to workers one by one - might be useful for a small number of slow tests. Larger numbers will allow the scheduler to submit consecutive chunks of tests to workers - allows reusing fixtures. Unlimited if not set. Fixes pytest-dev#855
amezin
added a commit
to amezin/pytest-xdist
that referenced
this issue
Dec 20, 2022
Maximum number of tests scheduled in one step. Setting it to 1 will force pytest to send tests to workers one by one - might be useful for a small number of slow tests. Larger numbers will allow the scheduler to submit consecutive chunks of tests to workers - allows reusing fixtures. Unlimited if not set. Fixes pytest-dev#855
amezin
added a commit
to amezin/pytest-xdist
that referenced
this issue
Dec 20, 2022
Maximum number of tests scheduled in one step. Setting it to 1 will force pytest to send tests to workers one by one - might be useful for a small number of slow tests. Larger numbers will allow the scheduler to submit consecutive chunks of tests to workers - allows reusing fixtures. Unlimited if not set. Fixes pytest-dev#855
|
I've solved this for myself with custom scheduler. It schedules long-running tests as early as possible while avoiding scheduling long-running tests one after the other (my long-running tests are marked with @amezin The work stealing scheduler is great idea for general purpose scheduler. The issue can be closed if you don't want to track my usecase. |
|
I think #857 will add some builtin support as a workaround, but the custom scheduler is indeed the optimal solution as it can be adapted for your specific test suite. I will be closing this then, thanks everyone for the discussion. |
nicoddemus
pushed a commit
that referenced
this issue
Dec 23, 2022
Maximum number of tests scheduled in one step. Setting it to 1 will force pytest to send tests to workers one by one - might be useful for a small number of slow tests. Larger numbers will allow the scheduler to submit consecutive chunks of tests to workers - allows reusing fixtures. Unlimited if not set. Fixes #855 Fixes #255
|
@mkoura out of curiosity, could you disable reordering workarounds, and try pytest-xdist |
|
Btw @amezin, feel free to kick off a new release if you would like to try it (see |
github-actions bot
added a commit
to luqasz/librouteros
that referenced
this issue
Feb 8, 2023
Bumps [pytest-xdist](https://github.com/pytest-dev/pytest-xdist) from 3.1.0 to 3.2.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-xdist/blob/master/CHANGELOG.rst">pytest-xdist's changelog</a>.</em></p> <blockquote> <h1>pytest-xdist 3.2.0 (2023-02-07)</h1> <h2>Improved Documentation</h2> <ul> <li><code>[#863](pytest-dev/pytest-xdist#863) <https://github.com/pytest-dev/pytest-xdist/issues/863></code>_: Document limitations for debugging due to standard I/O of workers not being forwarded. Also, mention remote debugging as a possible workaround.</li> </ul> <h2>Features</h2> <ul> <li> <p><code>[#855](pytest-dev/pytest-xdist#855) <https://github.com/pytest-dev/pytest-xdist/issues/855></code>_: Users can now configure <code>load</code> scheduling precision using <code>--maxschedchunk</code> command line option.</p> </li> <li> <p><code>[#858](pytest-dev/pytest-xdist#858) <https://github.com/pytest-dev/pytest-xdist/issues/858></code><em>: New <code>worksteal</code> scheduler, based on the idea of <code>work stealing <https://en.wikipedia.org/wiki/Work_stealing></code></em>. It's similar to <code>load</code> scheduler, but it should handle tests with significantly differing duration better, and, at the same time, it should provide similar or better reuse of fixtures.</p> </li> </ul> <h2>Trivial Changes</h2> <ul> <li><code>[#870](pytest-dev/pytest-xdist#870) <https://github.com/pytest-dev/pytest-xdist/issues/870></code>_: Make the tests pass even when <code>$PYTEST_XDIST_AUTO_NUM_WORKERS</code> is set.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/5c065198e98df484d8193a5fba5480db541fac37"><code>5c06519</code></a> Release 3.2.0</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/c695763e92951e20bd10c783c47884032826ea6d"><code>c695763</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/869">#869</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9373ddb3f841a009bc9669b514923b6ecba724e7"><code>9373ddb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/870">#870</a> from hroncok/delenv</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/8fd1bfd182e87f46e2c2ff6dbb43c0cd43d0cc00"><code>8fd1bfd</code></a> Tests: Unset PYTEST_XDIST_AUTO_NUM_WORKERS when the behavior without the envv...</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/017cc72b7090dc4bb7e7ad3d0caab024feb977a8"><code>017cc72</code></a> Document limitations for debugging as well as a workaround (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/867">#867</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/cf19f76d86aa149d21242da520879b8e0ee80013"><code>cf19f76</code></a> Fix minor typos in the documentation (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/866">#866</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/691a0751bf7081224287d13c0863fc981a838380"><code>691a075</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/865">#865</a> from amezin/fix-loadsched-tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/e9860923bf899b283627526bf9a23cb688204d42"><code>e986092</code></a> Fix some LoadScheduling tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/d1dfad3e927e225c967f16928b39eee43a3d6457"><code>d1dfad3</code></a> Implement work-stealing scheduler (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/862">#862</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9b0b5b1495b024940e3f5c71583711be46df255b"><code>9b0b5b1</code></a> Add --maxschedchunk CLI option (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/857">#857</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-xdist/compare/v3.1.0...v3.2.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) </details>
bors bot
added a commit
to microsoft/Qcodes
that referenced
this issue
Feb 8, 2023
4981: Update types-setuptools requirement from ~=67.1.0 to ~=67.2.0 r=jenshnielsen a=dependabot[bot] Updates the requirements on [types-setuptools](https://github.com/python/typeshed) to permit the latest version. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/python/typeshed/commits">compare view</a></li> </ul> </details> <br /> You can trigger a rebase of this PR by commenting ``@dependabot` rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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` 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) </details> 4982: Update pytest-xdist requirement from ~=3.1.0 to ~=3.2.0 r=jenshnielsen a=dependabot[bot] Updates the requirements on [pytest-xdist](https://github.com/pytest-dev/pytest-xdist) to permit the latest version. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-xdist/blob/master/CHANGELOG.rst">pytest-xdist's changelog</a>.</em></p> <blockquote> <h1>pytest-xdist 3.2.0 (2023-02-07)</h1> <h2>Improved Documentation</h2> <ul> <li><code>[#863](pytest-dev/pytest-xdist#863) <https://github.com/pytest-dev/pytest-xdist/issues/863></code>_: Document limitations for debugging due to standard I/O of workers not being forwarded. Also, mention remote debugging as a possible workaround.</li> </ul> <h2>Features</h2> <ul> <li> <p><code>[#855](pytest-dev/pytest-xdist#855) <https://github.com/pytest-dev/pytest-xdist/issues/855></code>_: Users can now configure <code>load</code> scheduling precision using <code>--maxschedchunk</code> command line option.</p> </li> <li> <p><code>[#858](pytest-dev/pytest-xdist#858) <https://github.com/pytest-dev/pytest-xdist/issues/858></code><em>: New <code>worksteal</code> scheduler, based on the idea of <code>work stealing <https://en.wikipedia.org/wiki/Work_stealing></code></em>. It's similar to <code>load</code> scheduler, but it should handle tests with significantly differing duration better, and, at the same time, it should provide similar or better reuse of fixtures.</p> </li> </ul> <h2>Trivial Changes</h2> <ul> <li><code>[#870](pytest-dev/pytest-xdist#870) <https://github.com/pytest-dev/pytest-xdist/issues/870></code>_: Make the tests pass even when <code>$PYTEST_XDIST_AUTO_NUM_WORKERS</code> is set.</li> </ul> <h1>pytest-xdist 3.1.0 (2022-12-01)</h1> <h2>Features</h2> <ul> <li> <p><code>[#789](pytest-dev/pytest-xdist#789) <https://github.com/pytest-dev/pytest-xdist/issues/789></code>_: Users can now set a default distribution mode in their configuration file:</p> <p>.. code-block:: ini</p> <pre><code>[pytest] addopts = --dist loadscope </code></pre> </li> <li> <p><code>[#842](pytest-dev/pytest-xdist#842) <https://github.com/pytest-dev/pytest-xdist/issues/842></code>_: Python 3.11 is now officially supported.</p> </li> </ul> <h2>Removals</h2> <ul> <li><code>[#842](pytest-dev/pytest-xdist#842) <https://github.com/pytest-dev/pytest-xdist/issues/842></code>_: Python 3.6 is no longer supported.</li> </ul> <h1>pytest-xdist 3.0.2 (2022-10-25)</h1> <p>Bug Fixes</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/5c065198e98df484d8193a5fba5480db541fac37"><code>5c06519</code></a> Release 3.2.0</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/c695763e92951e20bd10c783c47884032826ea6d"><code>c695763</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/869">#869</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9373ddb3f841a009bc9669b514923b6ecba724e7"><code>9373ddb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/870">#870</a> from hroncok/delenv</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/8fd1bfd182e87f46e2c2ff6dbb43c0cd43d0cc00"><code>8fd1bfd</code></a> Tests: Unset PYTEST_XDIST_AUTO_NUM_WORKERS when the behavior without the envv...</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/017cc72b7090dc4bb7e7ad3d0caab024feb977a8"><code>017cc72</code></a> Document limitations for debugging as well as a workaround (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/867">#867</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/cf19f76d86aa149d21242da520879b8e0ee80013"><code>cf19f76</code></a> Fix minor typos in the documentation (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/866">#866</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/691a0751bf7081224287d13c0863fc981a838380"><code>691a075</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/865">#865</a> from amezin/fix-loadsched-tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/e9860923bf899b283627526bf9a23cb688204d42"><code>e986092</code></a> Fix some LoadScheduling tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/d1dfad3e927e225c967f16928b39eee43a3d6457"><code>d1dfad3</code></a> Implement work-stealing scheduler (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/862">#862</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9b0b5b1495b024940e3f5c71583711be46df255b"><code>9b0b5b1</code></a> Add --maxschedchunk CLI option (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/857">#857</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-xdist/compare/v3.1.0...v3.2.0">compare view</a></li> </ul> </details> <br /> You can trigger a rebase of this PR by commenting ``@dependabot` rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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` 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) </details> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
github-actions bot
pushed a commit
to ryankanno/cookiecutter-py
that referenced
this issue
Feb 8, 2023
…tter.package_name}} Bumps [pytest-xdist](https://github.com/pytest-dev/pytest-xdist) from 3.1.0 to 3.2.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-xdist/blob/master/CHANGELOG.rst">pytest-xdist's changelog</a>.</em></p> <blockquote> <h1>pytest-xdist 3.2.0 (2023-02-07)</h1> <h2>Improved Documentation</h2> <ul> <li><code>[#863](pytest-dev/pytest-xdist#863) <https://github.com/pytest-dev/pytest-xdist/issues/863></code>_: Document limitations for debugging due to standard I/O of workers not being forwarded. Also, mention remote debugging as a possible workaround.</li> </ul> <h2>Features</h2> <ul> <li> <p><code>[#855](pytest-dev/pytest-xdist#855) <https://github.com/pytest-dev/pytest-xdist/issues/855></code>_: Users can now configure <code>load</code> scheduling precision using <code>--maxschedchunk</code> command line option.</p> </li> <li> <p><code>[#858](pytest-dev/pytest-xdist#858) <https://github.com/pytest-dev/pytest-xdist/issues/858></code><em>: New <code>worksteal</code> scheduler, based on the idea of <code>work stealing <https://en.wikipedia.org/wiki/Work_stealing></code></em>. It's similar to <code>load</code> scheduler, but it should handle tests with significantly differing duration better, and, at the same time, it should provide similar or better reuse of fixtures.</p> </li> </ul> <h2>Trivial Changes</h2> <ul> <li><code>[#870](pytest-dev/pytest-xdist#870) <https://github.com/pytest-dev/pytest-xdist/issues/870></code>_: Make the tests pass even when <code>$PYTEST_XDIST_AUTO_NUM_WORKERS</code> is set.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/5c065198e98df484d8193a5fba5480db541fac37"><code>5c06519</code></a> Release 3.2.0</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/c695763e92951e20bd10c783c47884032826ea6d"><code>c695763</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/869">#869</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9373ddb3f841a009bc9669b514923b6ecba724e7"><code>9373ddb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/870">#870</a> from hroncok/delenv</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/8fd1bfd182e87f46e2c2ff6dbb43c0cd43d0cc00"><code>8fd1bfd</code></a> Tests: Unset PYTEST_XDIST_AUTO_NUM_WORKERS when the behavior without the envv...</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/017cc72b7090dc4bb7e7ad3d0caab024feb977a8"><code>017cc72</code></a> Document limitations for debugging as well as a workaround (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/867">#867</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/cf19f76d86aa149d21242da520879b8e0ee80013"><code>cf19f76</code></a> Fix minor typos in the documentation (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/866">#866</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/691a0751bf7081224287d13c0863fc981a838380"><code>691a075</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/865">#865</a> from amezin/fix-loadsched-tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/e9860923bf899b283627526bf9a23cb688204d42"><code>e986092</code></a> Fix some LoadScheduling tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/d1dfad3e927e225c967f16928b39eee43a3d6457"><code>d1dfad3</code></a> Implement work-stealing scheduler (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/862">#862</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9b0b5b1495b024940e3f5c71583711be46df255b"><code>9b0b5b1</code></a> Add --maxschedchunk CLI option (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/857">#857</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-xdist/compare/v3.1.0...v3.2.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) </details>
github-actions bot
pushed a commit
to ryankanno/cookiecutter-py
that referenced
this issue
Feb 8, 2023
[//]: # (dependabot-start)⚠️ **Dependabot is rebasing this PR**⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps [pytest-xdist](https://github.com/pytest-dev/pytest-xdist) from 3.1.0 to 3.2.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-xdist/blob/master/CHANGELOG.rst">pytest-xdist's changelog</a>.</em></p> <blockquote> <h1>pytest-xdist 3.2.0 (2023-02-07)</h1> <h2>Improved Documentation</h2> <ul> <li><code>[#863](pytest-dev/pytest-xdist#863) <https://github.com/pytest-dev/pytest-xdist/issues/863></code>_: Document limitations for debugging due to standard I/O of workers not being forwarded. Also, mention remote debugging as a possible workaround.</li> </ul> <h2>Features</h2> <ul> <li> <p><code>[#855](pytest-dev/pytest-xdist#855) <https://github.com/pytest-dev/pytest-xdist/issues/855></code>_: Users can now configure <code>load</code> scheduling precision using <code>--maxschedchunk</code> command line option.</p> </li> <li> <p><code>[#858](pytest-dev/pytest-xdist#858) <https://github.com/pytest-dev/pytest-xdist/issues/858></code><em>: New <code>worksteal</code> scheduler, based on the idea of <code>work stealing <https://en.wikipedia.org/wiki/Work_stealing></code></em>. It's similar to <code>load</code> scheduler, but it should handle tests with significantly differing duration better, and, at the same time, it should provide similar or better reuse of fixtures.</p> </li> </ul> <h2>Trivial Changes</h2> <ul> <li><code>[#870](pytest-dev/pytest-xdist#870) <https://github.com/pytest-dev/pytest-xdist/issues/870></code>_: Make the tests pass even when <code>$PYTEST_XDIST_AUTO_NUM_WORKERS</code> is set.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/5c065198e98df484d8193a5fba5480db541fac37"><code>5c06519</code></a> Release 3.2.0</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/c695763e92951e20bd10c783c47884032826ea6d"><code>c695763</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/869">#869</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9373ddb3f841a009bc9669b514923b6ecba724e7"><code>9373ddb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/870">#870</a> from hroncok/delenv</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/8fd1bfd182e87f46e2c2ff6dbb43c0cd43d0cc00"><code>8fd1bfd</code></a> Tests: Unset PYTEST_XDIST_AUTO_NUM_WORKERS when the behavior without the envv...</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/017cc72b7090dc4bb7e7ad3d0caab024feb977a8"><code>017cc72</code></a> Document limitations for debugging as well as a workaround (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/867">#867</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/cf19f76d86aa149d21242da520879b8e0ee80013"><code>cf19f76</code></a> Fix minor typos in the documentation (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/866">#866</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/691a0751bf7081224287d13c0863fc981a838380"><code>691a075</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/865">#865</a> from amezin/fix-loadsched-tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/e9860923bf899b283627526bf9a23cb688204d42"><code>e986092</code></a> Fix some LoadScheduling tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/d1dfad3e927e225c967f16928b39eee43a3d6457"><code>d1dfad3</code></a> Implement work-stealing scheduler (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/862">#862</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9b0b5b1495b024940e3f5c71583711be46df255b"><code>9b0b5b1</code></a> Add --maxschedchunk CLI option (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/857">#857</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-xdist/compare/v3.1.0...v3.2.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) </details>
github-actions bot
pushed a commit
to ryankanno/py-golf-games
that referenced
this issue
Feb 9, 2023
[//]: # (dependabot-start)⚠️ **Dependabot is rebasing this PR**⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps [pytest-xdist](https://github.com/pytest-dev/pytest-xdist) from 3.1.0 to 3.2.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-xdist/blob/master/CHANGELOG.rst">pytest-xdist's changelog</a>.</em></p> <blockquote> <h1>pytest-xdist 3.2.0 (2023-02-07)</h1> <h2>Improved Documentation</h2> <ul> <li><code>[#863](pytest-dev/pytest-xdist#863) <https://github.com/pytest-dev/pytest-xdist/issues/863></code>_: Document limitations for debugging due to standard I/O of workers not being forwarded. Also, mention remote debugging as a possible workaround.</li> </ul> <h2>Features</h2> <ul> <li> <p><code>[#855](pytest-dev/pytest-xdist#855) <https://github.com/pytest-dev/pytest-xdist/issues/855></code>_: Users can now configure <code>load</code> scheduling precision using <code>--maxschedchunk</code> command line option.</p> </li> <li> <p><code>[#858](pytest-dev/pytest-xdist#858) <https://github.com/pytest-dev/pytest-xdist/issues/858></code><em>: New <code>worksteal</code> scheduler, based on the idea of <code>work stealing <https://en.wikipedia.org/wiki/Work_stealing></code></em>. It's similar to <code>load</code> scheduler, but it should handle tests with significantly differing duration better, and, at the same time, it should provide similar or better reuse of fixtures.</p> </li> </ul> <h2>Trivial Changes</h2> <ul> <li><code>[#870](pytest-dev/pytest-xdist#870) <https://github.com/pytest-dev/pytest-xdist/issues/870></code>_: Make the tests pass even when <code>$PYTEST_XDIST_AUTO_NUM_WORKERS</code> is set.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/5c065198e98df484d8193a5fba5480db541fac37"><code>5c06519</code></a> Release 3.2.0</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/c695763e92951e20bd10c783c47884032826ea6d"><code>c695763</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/869">#869</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9373ddb3f841a009bc9669b514923b6ecba724e7"><code>9373ddb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/870">#870</a> from hroncok/delenv</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/8fd1bfd182e87f46e2c2ff6dbb43c0cd43d0cc00"><code>8fd1bfd</code></a> Tests: Unset PYTEST_XDIST_AUTO_NUM_WORKERS when the behavior without the envv...</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/017cc72b7090dc4bb7e7ad3d0caab024feb977a8"><code>017cc72</code></a> Document limitations for debugging as well as a workaround (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/867">#867</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/cf19f76d86aa149d21242da520879b8e0ee80013"><code>cf19f76</code></a> Fix minor typos in the documentation (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/866">#866</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/691a0751bf7081224287d13c0863fc981a838380"><code>691a075</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/865">#865</a> from amezin/fix-loadsched-tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/e9860923bf899b283627526bf9a23cb688204d42"><code>e986092</code></a> Fix some LoadScheduling tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/d1dfad3e927e225c967f16928b39eee43a3d6457"><code>d1dfad3</code></a> Implement work-stealing scheduler (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/862">#862</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9b0b5b1495b024940e3f5c71583711be46df255b"><code>9b0b5b1</code></a> Add --maxschedchunk CLI option (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/857">#857</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-xdist/compare/v3.1.0...v3.2.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) </details>
kasperski95
pushed a commit
to software-mansion/protostar
that referenced
this issue
Feb 13, 2023
Bumps [pytest-xdist](https://github.com/pytest-dev/pytest-xdist) from 3.1.0 to 3.2.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest-xdist/blob/master/CHANGELOG.rst">pytest-xdist's changelog</a>.</em></p> <blockquote> <h1>pytest-xdist 3.2.0 (2023-02-07)</h1> <h2>Improved Documentation</h2> <ul> <li><code>[#863](pytest-dev/pytest-xdist#863) <https://github.com/pytest-dev/pytest-xdist/issues/863></code>_: Document limitations for debugging due to standard I/O of workers not being forwarded. Also, mention remote debugging as a possible workaround.</li> </ul> <h2>Features</h2> <ul> <li> <p><code>[#855](pytest-dev/pytest-xdist#855) <https://github.com/pytest-dev/pytest-xdist/issues/855></code>_: Users can now configure <code>load</code> scheduling precision using <code>--maxschedchunk</code> command line option.</p> </li> <li> <p><code>[#858](pytest-dev/pytest-xdist#858) <https://github.com/pytest-dev/pytest-xdist/issues/858></code><em>: New <code>worksteal</code> scheduler, based on the idea of <code>work stealing <https://en.wikipedia.org/wiki/Work_stealing></code></em>. It's similar to <code>load</code> scheduler, but it should handle tests with significantly differing duration better, and, at the same time, it should provide similar or better reuse of fixtures.</p> </li> </ul> <h2>Trivial Changes</h2> <ul> <li><code>[#870](pytest-dev/pytest-xdist#870) <https://github.com/pytest-dev/pytest-xdist/issues/870></code>_: Make the tests pass even when <code>$PYTEST_XDIST_AUTO_NUM_WORKERS</code> is set.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/5c065198e98df484d8193a5fba5480db541fac37"><code>5c06519</code></a> Release 3.2.0</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/c695763e92951e20bd10c783c47884032826ea6d"><code>c695763</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/869">#869</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9373ddb3f841a009bc9669b514923b6ecba724e7"><code>9373ddb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/870">#870</a> from hroncok/delenv</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/8fd1bfd182e87f46e2c2ff6dbb43c0cd43d0cc00"><code>8fd1bfd</code></a> Tests: Unset PYTEST_XDIST_AUTO_NUM_WORKERS when the behavior without the envv...</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/017cc72b7090dc4bb7e7ad3d0caab024feb977a8"><code>017cc72</code></a> Document limitations for debugging as well as a workaround (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/867">#867</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/cf19f76d86aa149d21242da520879b8e0ee80013"><code>cf19f76</code></a> Fix minor typos in the documentation (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/866">#866</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/691a0751bf7081224287d13c0863fc981a838380"><code>691a075</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/865">#865</a> from amezin/fix-loadsched-tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/e9860923bf899b283627526bf9a23cb688204d42"><code>e986092</code></a> Fix some LoadScheduling tests</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/d1dfad3e927e225c967f16928b39eee43a3d6457"><code>d1dfad3</code></a> Implement work-stealing scheduler (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/862">#862</a>)</li> <li><a href="https://github.com/pytest-dev/pytest-xdist/commit/9b0b5b1495b024940e3f5c71583711be46df255b"><code>9b0b5b1</code></a> Add --maxschedchunk CLI option (<a href="https://github-redirect.dependabot.com/pytest-dev/pytest-xdist/issues/857">#857</a>)</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest-xdist/compare/v3.1.0...v3.2.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
renovate bot
referenced
this issue
in ixm-one/pytest-cmake-presets
Mar 16, 2023
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [pytest-xdist](https://github.com/pytest-dev/pytest-xdist) ([changelog](https://pytest-xdist.readthedocs.io/en/latest/changelog.html)) | `3.1.0` -> `3.2.1` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>pytest-dev/pytest-xdist</summary> ### [`v3.2.1`](https://github.com/pytest-dev/pytest-xdist/blob/HEAD/CHANGELOG.rst#pytest-xdist-321-2023-03-12) [Compare Source](https://github.com/pytest-dev/pytest-xdist/compare/v3.2.0...v3.2.1) \=============================== ## Bug Fixes - `#​884 <https://github.com/pytest-dev/pytest-xdist/issues/884>`\_: Fixed hang in `worksteal` scheduler. ### [`v3.2.0`](https://github.com/pytest-dev/pytest-xdist/blob/HEAD/CHANGELOG.rst#pytest-xdist-320-2023-02-07) [Compare Source](https://github.com/pytest-dev/pytest-xdist/compare/v3.1.0...v3.2.0) \=============================== ## Improved Documentation - `#​863 <https://github.com/pytest-dev/pytest-xdist/issues/863>`\_: Document limitations for debugging due to standard I/O of workers not being forwarded. Also, mention remote debugging as a possible workaround. ## Features - `#​855 <https://github.com/pytest-dev/pytest-xdist/issues/855>`\_: Users can now configure `load` scheduling precision using `--maxschedchunk` command line option. - `#​858 <https://github.com/pytest-dev/pytest-xdist/issues/858>`*: New `worksteal` scheduler, based on the idea of `work stealing <https://en.wikipedia.org/wiki/Work_stealing>`*. It's similar to `load` scheduler, but it should handle tests with significantly differing duration better, and, at the same time, it should provide similar or better reuse of fixtures. ## Trivial Changes - `#​870 <https://github.com/pytest-dev/pytest-xdist/issues/870>`\_: Make the tests pass even when `$PYTEST_XDIST_AUTO_NUM_WORKERS` is set. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/ixm-one/pytest-cmake-presets). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS44LjAiLCJ1cGRhdGVkSW5WZXIiOiIzNS44LjAifQ==--> Signed-off-by: Renovate Bot <bot@renovateapp.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
folex
referenced
this issue
in fluencelabs/spell
Jun 6, 2023
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [pytest-xdist](https://github.com/pytest-dev/pytest-xdist) ([changelog](https://pytest-xdist.readthedocs.io/en/latest/changelog.html)) | `==2.5.0` -> `==3.3.1` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>pytest-dev/pytest-xdist</summary> ### [`v3.3.1`](https://github.com/pytest-dev/pytest-xdist/blob/HEAD/CHANGELOG.rst#pytest-xdist-331-2023-05-19) [Compare Source](https://github.com/pytest-dev/pytest-xdist/compare/v3.3.0...v3.3.1) \=============================== ## Bug Fixes - `#​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>`\__). ### [`v3.3.0`](https://github.com/pytest-dev/pytest-xdist/blob/HEAD/CHANGELOG.rst#pytest-xdist-330-2023-05-12) [Compare Source](https://github.com/pytest-dev/pytest-xdist/compare/v3.2.1...v3.3.0) \=============================== ## Features - `#​555 <https://github.com/pytest-dev/pytest-xdist/issues/555>`\_: Improved progress output when collecting nodes to be less verbose. ### [`v3.2.1`](https://github.com/pytest-dev/pytest-xdist/blob/HEAD/CHANGELOG.rst#pytest-xdist-321-2023-03-12) [Compare Source](https://github.com/pytest-dev/pytest-xdist/compare/v3.2.0...v3.2.1) \=============================== ## Bug Fixes - `#​884 <https://github.com/pytest-dev/pytest-xdist/issues/884>`\_: Fixed hang in `worksteal` scheduler. ### [`v3.2.0`](https://github.com/pytest-dev/pytest-xdist/blob/HEAD/CHANGELOG.rst#pytest-xdist-320-2023-02-07) [Compare Source](https://github.com/pytest-dev/pytest-xdist/compare/v3.1.0...v3.2.0) \=============================== ## Improved Documentation - `#​863 <https://github.com/pytest-dev/pytest-xdist/issues/863>`\_: Document limitations for debugging due to standard I/O of workers not being forwarded. Also, mention remote debugging as a possible workaround. ## Features - `#​855 <https://github.com/pytest-dev/pytest-xdist/issues/855>`\_: Users can now configure `load` scheduling precision using `--maxschedchunk` command line option. - `#​858 <https://github.com/pytest-dev/pytest-xdist/issues/858>`*: New `worksteal` scheduler, based on the idea of `work stealing <https://en.wikipedia.org/wiki/Work_stealing>`*. It's similar to `load` scheduler, but it should handle tests with significantly differing duration better, and, at the same time, it should provide similar or better reuse of fixtures. ## Trivial Changes - `#​870 <https://github.com/pytest-dev/pytest-xdist/issues/870>`\_: Make the tests pass even when `$PYTEST_XDIST_AUTO_NUM_WORKERS` is set. ### [`v3.1.0`](https://github.com/pytest-dev/pytest-xdist/blob/HEAD/CHANGELOG.rst#pytest-xdist-310-2022-12-01) [Compare Source](https://github.com/pytest-dev/pytest-xdist/compare/v3.0.2...v3.1.0) \=============================== ## Features - `#​789 <https://github.com/pytest-dev/pytest-xdist/issues/789>`\_: Users can now set a default distribution mode in their configuration file: .. code-block:: ini [pytest] addopts = --dist loadscope - `#​842 <https://github.com/pytest-dev/pytest-xdist/issues/842>`\_: Python 3.11 is now officially supported. ## Removals - `#​842 <https://github.com/pytest-dev/pytest-xdist/issues/842>`\_: Python 3.6 is no longer supported. ### [`v3.0.2`](https://github.com/pytest-dev/pytest-xdist/blob/HEAD/CHANGELOG.rst#pytest-xdist-302-2022-10-25) [Compare Source](https://github.com/pytest-dev/pytest-xdist/compare/v2.5.0...v3.0.2) \=============================== ## Bug Fixes - `#​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>`\_: 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>`\_: 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>`\_: Document the `pytest_xdist_auto_num_workers` hook. - `#​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>`\_: Document the `-n logical` option. ## Features - `#​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>`\_: 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 `min(n_tests, n_workers)` times, no matter how many other tests there are. With the old algorithm (before v1.14), if there are enough tests not using the fixture, the fixture was created only once. So restore the old behavior for typical cases where the number of tests is much greater than the number of workers (or, strictly speaking, when there are at least 2 tests for every node). ## Removals - `#​468 <https://github.com/pytest-dev/pytest-xdist/issues/468>`\_: The `--boxed` command-line option has been removed. If you still need this functionality, install `pytest-forked <https://pypi.org/project/pytest-forked>`\__ separately. ## Trivial Changes - `#​468 <https://github.com/pytest-dev/pytest-xdist/issues/468>`\_: The `py` dependency has been dropped. - `#​822 <https://github.com/pytest-dev/pytest-xdist/issues/822>`\_: Replace internal usage of `py.log` with a custom solution (but with the same interface). - `#​823 <https://github.com/pytest-dev/pytest-xdist/issues/823>`\_: Remove usage of `py._pydir` as an rsync candidate. - `#​824 <https://github.com/pytest-dev/pytest-xdist/issues/824>`\_: Replace internal usages of `py.path.local` by `pathlib.Path`. </details> --- ### Configuration 📅 **Schedule**: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/fluencelabs/spell). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS40MC4wIiwidXBkYXRlZEluVmVyIjoiMzUuOTUuMSIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
allisonkarlitskaya
added a commit
to allisonkarlitskaya/cockpit
that referenced
this issue
Jun 9, 2023
pytest-xdist sends large chunks of tasks to the workers to reduce latency, but since our tasks are long, this isn't helpful. It also means that we can end up with a large string of very slow tests on one worker. Disable it, if possible. pytest-dev/pytest-xdist#855
allisonkarlitskaya
added a commit
to allisonkarlitskaya/cockpit
that referenced
this issue
Jun 16, 2023
pytest-xdist sends large chunks of tasks to the workers to reduce latency, but since our tasks are long, this isn't helpful. It also means that we can end up with a large string of very slow tests on one worker. Disable it, if possible. pytest-dev/pytest-xdist#855
allisonkarlitskaya
added a commit
to allisonkarlitskaya/cockpit
that referenced
this issue
Jun 16, 2023
pytest-xdist sends large chunks of tasks to the workers to reduce latency, but since our tasks are long, this isn't helpful. It also means that we can end up with a large string of very slow tests on one worker. Disable it, if possible. pytest-dev/pytest-xdist#855
martinpitt
pushed a commit
to cockpit-project/cockpit
that referenced
this issue
Jun 17, 2023
](https://renovatebot.com){kind=link}
pytest-xdist sends large chunks of tasks to the workers to reduce latency, but since our tasks are long, this isn't helpful. It also means that we can end up with a large string of very slow tests on one worker. Disable it, if possible. pytest-dev/pytest-xdist#855
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The PR #812 that implemented new batch distribution logic (and that is now released in 3.0.2) disregards long-running tests.
I have several modules with long-running tests and many of these tests are now scheduled on single worker, instead of being distributed evenly across multiple workers. As a result, total runtime of my testsuite more than doubled from ~ 2.5 hours to 5+ hours.
Are there any workarounds to bring back the original round-robin scheduling?
cc @amezin
The text was updated successfully, but these errors were encountered: