pytest-xdist
pytest-xdist copied to clipboard
pytest plugin for distributed testing and loop-on-failures testing modes.
Steps to reproduce 1. create a folder names tests 2. create a file `test_foo.py` with the content `def test_1(): assert True` 3. create a file `test_bar.py` with the content ```py...
For smaller number of tests, setting up 12 workers in 12 cores in my machine is overkill, is there a way to have pytest run xdist/parallel testing only if the...
I am not using the `--rsyncdir` command-line option, yet I'm seeing this deprecation warning: ``` .../site-packages/xdist/plugin.py:259: DeprecationWarning: The --rsyncdir command line argument and rsyncdirs config variable are deprecated. The rsync...
## Issue Description When running `pytest-asyncio` with `pytest-xdist`, my tests consistently hang between 90-100% completion. I suspect there might be an issue with resource acquisition not being properly managed at...
I'm not sure if there are other use cases, but the relevant change I'm talking about is a byproduct of #778. With #778, we are now ordering tests based on...
As the doc said: ``` This will make sure test1 and TestA::test2 will run in the same worker. Tests without the xdist_group mark are distributed normally as in the --dist=load...
updates: - [github.com/astral-sh/ruff-pre-commit: v0.5.4 → v0.5.5](https://github.com/astral-sh/ruff-pre-commit/compare/v0.5.4...v0.5.5)
build(deps): bump hynek/build-and-inspect-python-package from 2.7 to 2.8 in the github-actions group
Bumps the github-actions group with 1 update: [hynek/build-and-inspect-python-package](https://github.com/hynek/build-and-inspect-python-package). Updates `hynek/build-and-inspect-python-package` from 2.7 to 2.8 Release notes Sourced from hynek/build-and-inspect-python-package's releases. v2.8.0 Changed We now use uv's new uv cache prune...
`--exitfirst` and `--last-failed` work fine with xdist. Sadly stepwise doesn't (#458). One might think that stepwise could be emulated by running with both exitfirst and last-failed, however it looks like...
The current implementation of `-n auto` is not working as hoped on high-performance computing environments where processes are assigned a number of cores they can use. For example, when running...