pytest-xdist icon indicating copy to clipboard operation
pytest-xdist copied to clipboard

pytest plugin for distributed testing and loop-on-failures testing modes.

Results 136 pytest-xdist issues
Sort by recently updated
recently updated
newest added

In pypa/distutils#183, I've stumbled onto an issue with xdist. In that issue, distutils/setuptools are moving from a stdout-based logging system to the Python logging framework. As a result, the `quiet()`...

When pytest xdist is used, pytest logs are not output to the console and log files. Is this block compatible

bug

test_5.py file content ```python import logging logger = logging.getLogger(__file__) def test_1(): logger.info('123123') def test_2(): logger.info('123123') def test_3(): logger.info('123123') def test_4(): logger.info('123123') ``` pytest.ini ``` [pytest] log_cli=true log_cli_level=DEBUG log_format = %(asctime)s...

Workers did not share config.option from controller Fixes: #800

bug

My commands :pytest.main(['-q', "--html=report.html", '-n=4']) I have not set pytest "-- color=yes" Using xdits causes the report color output to be ansi characters. Unrecognized html report ![image](https://user-images.githubusercontent.com/42427586/196027113-5637c57e-4a9c-45cd-a88f-43df95a4cfc6.png) I want to...

I tried with -n auto and intentionally failed some unit tests to check if it aborts GitHub action but it doesn't while simple pytest does abort.

I am fairly new to this project. I very recently migrated a software project test-suite from nosetest to pytest, mainly because of the Xdist benefits I had heard of. The...

question

I am parametrizing a test class and scheduling tests with `--dist loadscope`. I was expecting the effect that every parameter combination will be treated as a separate class by pytest....

This is bizarre, but locally on macOS 12.5.1 M1 a crashed worker exits nonzero, which is correct. But on Ubuntu 22.04 (GitHub-hosted action runner), a crashed worker exits zero and...

I very recently started getting the "Different tests were collected between gwX and gwY" error when running tests with multiple workers. It only happens under specific circumstances though. The circumstances...