pytest-dev / pytest-dev/pytest-xdist
`--dist` and `--numprocesses` flags conflict
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 287
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 2
Description
I would like to use --dist=worksteal with paralellism enabled. I seem to be getting either parallelism or work stealing, but not both together.
I've followed the advice here to print out all of the pytest configuration options:
def test_answer(pytestconfig):
for item_name in dir(pytestconfig.option):
if not item_name.startswith("_"):
print(f"{item_name}: {getattr(pytestconfig.option, item_name)}")
assert 0 # to see what was printed
--dist=worksteal only:
$ pytest --dist=worksteal test.py | grep "dist:"
dist: worksteal
With parallelism enabled:
$ pytest --numprocesses=auto --dist=worksteal test.py | grep "dist:"
dist: no
$ pytest --dist=worksteal --numprocesses=auto test.py | grep "dist:"
dist: no
Are my expectations wrong? Is there somewhere else I should be looking to check that workstealing is active?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported commands against test.py, comparing pytest's printed configuration options for --dist=worksteal and --numprocesses=auto. Trace the command-line handling that produces dist: no; done means establishing whether the flags can coexist and either correcting that behavior or documenting the expected configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100